[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse.org-architecture-council] JEP 336: deprecate pack200
|
Also, as one can see from the history of the pack200's spec (https://docs.oracle.com/javase/10/docs/specs/pack-spec.html), it had to evolve a couple of times to follow the evolutions of the class file format.
So by maintaining pack200 support, we're not only talking about maintaining an implementation of the spec, but also the spec itself to follow future evolutions of Java... and my guess is that it's an order of magnitude harder.
Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation 📱 (+33) 642 028 039 | 🐦 @mikbarbero
jmod is unspeced and can be different from jdk release to jdk release so a jmod from Java9 might not be readable in jdk11.
Tom Von meinem iPhone gesendet _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
|
Attachment:
signature.asc
Description: Message signed with OpenPGP