Re: [nosql-dev] Time to Move API and RI to Java 11

[Werner Keil <werner.keil@xxxxxxx>]

Otavio,

 

What exactly does that mean?

Only the Jenkins build Job, I guess that is fine to use only Java 11 or even higher, but the Minimum

API source Level for Jakarta EE 9.1 is not 11:

The APIs will continue to be compiled at the Java SE 8 level. The APIs need to be usable by both Java SE 8 and Java SE 11. Thus, keeping the same Java SE 8 source/target level for the APIs will still be required.

see

https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9.1ReleasePlan

 

We may have more freedom in the CI (there’s no RI anymore ;-) if abandoning Java 8 there was beneficial, I guess the project could do that, but for the API it must align with Jakarta EE so unless Jakarta EE 10 or 11 (or whenever Jakarta NoSQL was ready to join a profile there) changed that, we must Keep the API compatible with the minimal JDK mandated by Jakarta EE.

 

Werner

 

Von: Otavio Santana
Gesendet: Montag, 29. März 2021 20:58
An: jnosql developer discussions; nosql developer discussions
Betreff: [nosql-dev] Time to Move API and RI to Java 11

 

Hello everyone, we've seen the Jakarta EE 9.1 that uses Java 11 as a minimum requirement.

The Weld implementation will use Java 11 as well:

• https://twitter.com/jbossweld/status/1372567415297556481
• https://twitter.com/jbossweld/status/1374014154298773505

Thus, I believe that it is time to move both the API and the JNoSQL to use Java 11 as a minimum requirement.

Right now, we have Jenkins instances to run Java 8 and Java 11.
Once Java 11 will be the default, it will delete the Java 8 Job.

• https://ci.eclipse.org/jnosql/
• https://ci.eclipse.org/nosql/

 

--

Otávio Santana

 

 

twitter: http://twitter.com/otaviojava

site:     http://about.me/otaviojava