That’s not correct, because whereever the definitions of modules like " java.servlet", "java.json", etc. existed in Jakarta EE 8 this must also be changed just like the packages.
See
https://docs.google.com/spreadsheets/d/1g8jYG0JixO3wzZkpeyU1LMIQRhbnZ76kGtdMFE8mieE/edit?usp=sharing
Maybe Scott was a bit ahead of himself sending it to ALL project leads, but especially those that already had a module declaration in Jakarta EE 8 and have not changed that to "jakarta.*" must also do that.
Those with a wrong automatic module name could also be "lazy" and simply remove that, I don’t think any full module-info wasn’t changed or newly introduced correctly, and especially those must not be destroyed because many of them like Activation are used in other specs like Mail, so IMO we could throw those options at them if that is what Scott suggested, but not sure, if the project leads may vote or if they should simply apply them, Option F is the preferred one by the Spec Committee and also what I mentioned here.
Only 8 specs would have to do anything, of these at least 4 already had modules defined in Jakarta EE 8, so they should leave them under the new namespace, the others could also just remove the automatic declaration.
Werner
Our goal was to change the license and rename the Java packages. Please do not prolong the work with more ambitions.
I sent an email to the project leads list asking for feedback in the comments section of the doc that I just added.
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
