Re: [ee4j-community] Some guidelines for Maintenance Releases (MRs) of J

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Werner Keil wrote on 01/ 8/18 01:40 PM:

Will,

Thanks for the update.

Can you tell us what this means for backward-compatibility and ease of adoption?

>   Oracle does not recommend or support use the JCP process for any future Java EE 8 functional enhancements.

effectively means it does not support the use of the javax.* namespace either.

No, that's not what it means.  Please see the EE4J FAQ.

What does that mean for JSON-B (Yasson 1.1 still claims to implement JSR 367 without change) or more drastically EclipseLink 3.x? https://projects.eclipse.org/projects/rt.eclipselink/releases/3.0.0

There are 3 quarterly releases planned for EclipseLink 3. At least 3.0.0 as  Major release (API breakage) 

What does that mean for JPA? The relatively small MR of JPA 2.2 would not offer  Full Java SE 9 compatibility for EclipseLink 3 without an API upgrade likely also something like JPA 3 or at least something that declares full Java SE 9 modules. 

Where is this supposed to happen and under what package name, javax.persistence or something else?

Functional enhancements of these APIs should occur as part of the EE4J project, using whatever process is defined there.  Again, see the EE4J FAQ.