JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API (original) (raw)
mark.reinhold at oracle.com mark.reinhold at oracle.com
Fri Jun 15 14:23:11 UTC 2018
- Previous message: JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API
- Next message: JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2018/6/14 16:56:41 -0700, Emmanuel Bourg <ebourg at apache.org>:
...
Do I understand correctly that pack200 will be in JDK 11 but might be removed in a later release?
Yes.
If maintaining this technology is a burden for Oracle, could community involvement help reverse this decision?
Possibly. As noted in the JEP, however, Pack200 is a complex and elaborate technology that’s tightly coupled to the class-file format and the JAR-file format, both of which continue to evolve. This isn’t a reasonably-separable component that can be maintained more or less at its own pace. If one or more non-Oracle contributors were to step up to maintain Pack200 then they’d need to commit to staying on top of it and participating in most every six-month feature release.
- Mark
- Previous message: JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API
- Next message: JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]