[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] Fwd: Re: JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API
- From: Peter Firmstone <peter.firmstone@xxxxxxxxxxx>
- Date: Fri, 29 Jun 2018 17:31:25 +1000
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:220.127.116.11) Gecko/20120306 Thunderbird/3.1.20
-------- Original Message --------
Subject: Re: JEP proposed to target JDK 11: 336: Deprecate the Pack200
Tools and API
Date: Fri, 29 Jun 2018 17:27:07 +1000
From: Peter <jini@xxxxxxxxxxx>
CC: P2 developer discussions <p2-dev@xxxxxxxxxxx>
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
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.
On 27/06/2018 4:05 AM, mark.reinhold@xxxxxxxxxx wrote:
2018/6/25 8:54:48 -0700, daniel_megert@xxxxxxxxxx:
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
Thatâs a legal question, which Iâm not qualified to answer.