|Re: [p2-dev] Pack200 compression|
I think p2 will currently just fail if pack200 is absent. It definitely could be smart enough to ignore pack200 artifacts if it knows it can't unpack them, but I don't think that's currently the case. In fact there was some rather questionable logic in the code that if some pack200 artifact is downloaded, but it can't be unpacked, p2 will download it again, assuming that the artifact it downloaded is corrupt, and it will try that 200 times (I believe that's the magic number) before it tries to just download the plain .jar artifact, if available. This of course leads to horrible performance.
But I agree that if there were a Java unpack200 library p2 could use, that would be better and perhaps perform better than execing a process.
Keep in mind that one of the "smart" aspects of the current
design of using the JRE's pack200 is that you could update your
IDE from say a version that currently requires Java 8 but is
running with Java 9 to a version that actually requires Java 9.
If the library for unpack200 is included in the IDE itself, it
would only know about unpacking Java 8 and wouldn't be able to
unpack Java 9 (leading to the above horrible performance problem).
On 26.06.2018 09:11, Mickael Istria wrote:
Back to the top