JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API (original) (raw)

Daniel Megert daniel_megert at ch.ibm.com
Mon Jun 25 15:54:48 UTC 2018

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?

Dani

From: Daniel Megert/Zurich/IBM To: mark.reinhold at oracle.com Date: 15.06.2018 08:51 Subject: Re: JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API

Hi Mark

Can you please comment on http://mail.openjdk.java.net/pipermail/jdk-dev/2018-June/001382.html.

Dani

From: mark.reinhold at oracle.com To: jdk-dev at openjdk.java.net Date: 15.06.2018 01:07 Subject: Re: JEP proposed to target JDK 11: 336: Deprecate the Pack200 Tools and API Sent by: "jdk-dev" <jdk-dev-bounces at openjdk.java.net>

2018/6/7 15:35:15 -0700, mark.reinhold at oracle.com:

The following JEP is proposed to target JDK 11:

336: Deprecate the Pack200 Tools and API http://openjdk.java.net/jeps/336

Feedback on this proposal is more than welcome, as are reasoned objections. If no such objections are raised by 23:00 UTC on Thursday, 14 June, or if they're raised and then satisfactorily answered, then per the JEP 2.0 process proposal [1] I'll target this JEP to JDK 11.

Hearing no objections, I?ve targeted this JEP to JDK 11.

More information about the jdk-dev mailing list