In the Spec Committee minutes we made a couple of decisions, e.g.
The goal of 9.1 is to NOT release new API artifacts. We are open for specs to do minor updates, thus release a new artifact if they have to in order to support Java SE 11.
That already implies, if an API does not have anything new, it won’t be changed and is of course as backward-compatible as 9.0.
If e.g. a spec like CDI wishes to better support Java 11 or modularity (CDI currently does not even declare an Automatic-Module-Name) it may do so, but there is no obligation to release a new API just for the sake of a module-definition.
Btw. those are the kinds of decisions not made via email, so if a committee had so few participants in such call that it missed a quorum, it could not make, so attending calls whenever possible is important ;-)
Werner
Thank you, Rudy. Concise and unambiguous, as I love it. :-)
-Markus
Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Rudy De Busscher
Gesendet: Samstag, 26. Dezember 2020 18:18
An: jakartaee-platform developer discussions
Betreff: Re: [jakartaee-platform-dev] Java 11
> Specification APIs must be compiled to Java SE 8
Recently it was decided that Java 11 will be mandatory for Jakarta EE 9.1, but I wonder what this actually allows / enforces. So please officially clarify (please only official decision but not "I think" or "My 2 cents are" or other non-binding comments…):
* Specifications MAY use Java 11 specific APIs and Java 11 key words like "var"?
-or-
* Specifications MUST still be able to be used on JRE 8?
Thanks!
-Markus
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev