| Re: [jakartaee-platform-dev] Java 11 |
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 Von: Markus KARG 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 > Specification APIs must be compiled to Java SE 8 as decided on Jakarta EE Platform, December 15th. see https://eclipse-ee4j.github.io/jakartaee-platform/minutes/2020-12-15.html Regards Rudy On Sat, 26 Dec 2020 at 18:10, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
_______________________________________________ |