4.0.x build issues (for use with Java 17) - #1060
Conversation
- org.apache.felix:maven-bundle-plugin:4.0.0:manifest failed.: ConcurrentModificationException - The plugin io.quarkus:quarkus-maven-plugin:3.2.9.Final has unmet prerequisites: Required Java version 17 is not met by current version: 11.0.32
|
Why the CI on 11 builds then sucessful? |
|
API/ IMPl still use Java 11:
Quarkus Extension use 17:
|
| </property> | ||
| </systemProperties> | ||
| <argLine>-Djava.locale.providers=COMPAT</argLine> | ||
| <argLine>-Djava.locale.providers=COMPAT --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.security=ALL-UNNAMED</argLine> |
There was a problem hiding this comment.
May not be needed anymore. I could remove.
|
CI is working on 11 |
|
Don't understand what's going on....? I'm only running
|
|
yeah 4.0 is Java 11 i thought 4.1 was 17? |
|
CI runs Please try yourself. I'm not able to get it to run with Java 11. Edit: CI must somehow switch to Java 17, I believe. |
|
4.0 is Java 11 |
|
The CI for 4.0.x already runs as 11? See: myfaces/.github/workflows/myfaces-ci.yml Lines 57 to 64 in d7f25e5 |
|
I mean the mvn clean Install before the deploy? |
|
OK added PR: #1060 |
|
OK confirmed it says Quarkus 3.2 supports JDK 11 but let me try 3.2.12 its the last version of 3.2.X |
|
ahh it looks like 2.16.12.Final is the last Quarkus to support Java 11. |
|
crap this looks like a bigger change than we want. @tandraschko should we just commetn out the Quarkus Extension in this 4.0.X branch? Or build with 17 which should set the MyFaces to 11 and allow Quarkus Extension to build with 17 fine? |
|
No Idea
|
|
TBH i would Release without quarkus, Just remove it from root pom. Quarkus user are more bleeding edge, they can just go to 4.1?! |
|
Can you add it to your PR @melloware? |
|
yep i totally agree @tandraschko fixing my PR now |
|
@volosied all fixed! Closing this PR |
4.0.x requires a min of Java 11, but it doesn't build with it due to error:
If I use Java 17, then I get:
I've updated the dependencies to use Java 17 (but still have the source/target set to 11). Inadvertently, Java 17 caused number converter errors which I've also fixed.