search

eclipse / microprofile-parent

Apache License 2.0
2 stars 19 forks source link

Update Java version to 11 #65

Closed Emily-Jiang closed 2 years ago

Emily-Jiang commented 2 years ago

Since the source and binary java level for Jakarta EE 10 Core Profile is 11, we need to bump our minimum Java version to 11 as well.

Emily-Jiang commented 2 years ago

Is the intent to produce binaries compatible with Java 11+ only, even if the specs haven't changed to require Java 11 features?

I'm referring to this from the mailing list:

"A MicroProfile specification should not change versions just for a new Jakarta EE version unless the MicroProfile specification must change to support the new Jakarta EE version. It is possible for a MicroProfile specification version to work on multiple versions of Jakarta EE."

This talks about Jakarta EE version not Java version. e.g. Config 3.0 works with either Jakarta EE 10 or 9.1. OpenAPI 3.1 will only work with Jakarta EE 10 not Jakarta EE 9.1.

Emily-Jiang commented 2 years ago

If a class imports a Java class whose binary is 11, I don't think you can use Java 8 to compile this class as it does not understand Java 11.

bjhargrave commented 2 years ago

I don't this conforms to the vote mentioned above. Each project needs to decide to update Jakarta EE versions and Java target versions on its own. The parent pom should not be pushing this onto all projects.

Emily-Jiang commented 2 years ago

@bjhargrave I have added more description to this pom.xml to specify the Java version update and Jakarta EE 10 alignment.