Handle jar files properly
ivan-gavran opened this issue · 7 comments
As uncovered in Issue #209, modelator does not handle storing jar files properly.
One suggested option was to use appdirs to store files.
Another suggestion was to auto-fetch releases: we should be careful about that, as we know that TLC can change a release without giving it a separate name (and thus we lose control over what's there in Modelator).
I think it might be worth filing (or updating) an issue on the tlatools repo explaining why their unstable release process is so problematic. It probably won't fix our short-term needs, but should it could help fix this for us down the line and it will put beneficial pressure towards more sustainable behavior on this key feature of the TLA ecosystem.
TLC has a stable release from February 2022. We can work with that.
@andrey-kuprianov @hvanz @ivan-gavran what do you think?
Aha, good to know! (Didn't know that that changed). Yes, in that case, I agree that pulling a release is a good idea.
Nothing changed. They just did a stable release in February. They still do their unstable releases by overwriting previous unstable releases.
OK, now I understand: the one for February is guaranteed to be stable, but the still have an unstable release that keeps being overwritten.
I think it makes sense to proceed by downloading releases as dependencies and not storing them in our repo.
I think it might be worth filing (or updating) an issue on the tlatools repo explaining why their unstable release process is so problematic. It probably won't fix our short-term needs, but should it could help fix this for us down the line and it will put beneficial pressure towards more sustainable behavior on this key feature of the TLA ecosystem.
I think it might be worth filing (or updating) an issue on the tlatools repo explaining why their unstable release process is so problematic. It probably won't fix our short-term needs, but should it could help fix this for us down the line and it will put beneficial pressure towards more sustainable behavior on this key feature of the TLA ecosystem.
I think it might be worth filing (or updating) an issue on the tlatools repo explaining why their unstable release process is so problematic. It probably won't fix our short-term needs, but should it could help fix this for us down the line and it will put beneficial pressure towards more sustainable behavior on this key feature of the TLA ecosystem.
@shonfeder , I think I already once commented on that issue, but couldn't possibly find it now. Do you have it somewhere on the radar?
Maybe this one? tlaplus/tlaplus#668