JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API

Peter jini at zeus.net.au
Fri Jun 29 07:27:07 UTC 2018


We've been discussing this on the Eclipse p2 dev list.

The following has been proposed:

   1. Deprecate and remove the C++ Pack200 implementation and command
      line tools.
   2. Maintain the Pack200 standard and Pack200 implementation written
      in java, including adding support for Java 9 and 11 new pool
      constants and attributes.
   3. Don't deprecate the Pack200 standard or the Java library api or
      the java implementation.

I'll sign up to maintain the java implementation.

Regards,

Peter Firmstone.

On 27/06/2018 4:05 AM, mark.reinhold at oracle.com wrote:
> 2018/6/25 8:54:48 -0700, daniel_megert at ch.ibm.com:
>> Sorry, didn't see your reply.
>>
>>> Is Eclipse willing to sign up to maintain this technology?
>> If someone steps up to do so, yes. I think Peter has interest to do so.
>> The question is: is it legally allowed to implement and ship a deprecated
>> specification?
> That’s a legal question, which I’m not qualified to answer.
>
> - Mark



More information about the jdk-dev mailing list