JEPs proposed to target JDK 14: 345, 361, 363, 364, 365, & 367 (original) (raw)
Peter Firmstone peter.firmstone at zeus.net.au
Fri Nov 8 23:38:17 UTC 2019
- Previous message: JEPs proposed to target JDK 14: 345, 361, 363, 364, 365, & 367
- Next message: JEPs proposed to target JDK 14: 345, 361, 363, 364, 365, & 367
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
WRT Jep 367 Pack200 tools, I'm planning to copy the latest java implementation and tests from openjdk and set up repository on github and release on Maven Central, so the code can be maintained and updated, albeit at a slower pace than would be required or acceptable for OpenJDK, but would be sufficient for long term maintenance and transition. I understand the api code will no longer be available in Java 14 onwards, however a URL provider should be sufficient to continue to allow unpacking of pack200 files.
Any advice or recommendations will be appreciated.
Regards,
Peter Firmstone.
On 11/9/2019 4:28 AM, mark.reinhold at oracle.com wrote:
2019/10/31 15:44:04 -0700, mark.reinhold at oracle.com:
The following JEPs are proposed to target JDK 14:
345: NUMA-Aware Memory Allocation for G1 http://openjdk.java.net/jeps/345 361: Switch Expressions (Standard) http://openjdk.java.net/jeps/361 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector http://openjdk.java.net/jeps/363 364: ZGC on macOS http://openjdk.java.net/jeps/364 365: ZGC on Windows http://openjdk.java.net/jeps/365 367: Remove the Pack200 Tools and API http://openjdk.java.net/jeps/367 Hearing no objections, I’ve targeted these JEPs to JDK 14 except for JEP 365 (ZGC on Windows), which was returned to Candidate by its owner. - Mark
- Previous message: JEPs proposed to target JDK 14: 345, 361, 363, 364, 365, & 367
- Next message: JEPs proposed to target JDK 14: 345, 361, 363, 364, 365, & 367
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]