Currently, the Eclipse JNoSQL specification uses Java 11 API. However, the main goal of Jakarta EE 11 is to use the latest LTS (Long-Term Support) version of Java. Therefore, we need to update the Eclipse JNoSQL API to Java 17 to keep up with the newest version of Java.
To achieve this goal, we need to update the POM.xml file to specify the Maven version that supports Java 17. Additionally, we should remove the Java 11 GitHub action and replace it with a Java 17 action.
As an implementation of Jakarta Data and Jakarta NoSQL, we need to follow the latest Java SE 17 to be ready for Java 21. This issue is an excellent opportunity for the first contribution to Eclipse JNoSQL, and we encourage the community to help us update the API to Java 17.
Tasks:
Update POM.xml to specify Maven version that supports Java 17.
Remove Java 11 GitHub action.
Add Java 17 GitHub action.
Note: The goal of Jakarta EE 11 is to use the latest Java LTS release, which is Java 17. We should aim to use Java 17 to keep the Eclipse JNoSQL specification up-to-date.
Currently, the Eclipse JNoSQL specification uses Java 11 API. However, the main goal of Jakarta EE 11 is to use the latest LTS (Long-Term Support) version of Java. Therefore, we need to update the Eclipse JNoSQL API to Java 17 to keep up with the newest version of Java.
To achieve this goal, we need to update the POM.xml file to specify the Maven version that supports Java 17. Additionally, we should remove the Java 11 GitHub action and replace it with a Java 17 action.
As an implementation of Jakarta Data and Jakarta NoSQL, we need to follow the latest Java SE 17 to be ready for Java 21. This issue is an excellent opportunity for the first contribution to Eclipse JNoSQL, and we encourage the community to help us update the API to Java 17.
Tasks:
Note: The goal of Jakarta EE 11 is to use the latest Java LTS release, which is Java 17. We should aim to use Java 17 to keep the Eclipse JNoSQL specification up-to-date.