Skip to content

4.0.x build issues (for use with Java 17) - #1060

Closed
volosied wants to merge 3 commits into
apache:4.0.xfrom
volosied:4.0.x-build-issues
Closed

4.0.x build issues (for use with Java 17)#1060
volosied wants to merge 3 commits into
apache:4.0.xfrom
volosied:4.0.x-build-issues

Conversation

@volosied

Copy link
Copy Markdown
Contributor

4.0.x requires a min of Java 11, but it doesn't build with it due to error:

[ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:3.2.9.Final:build (default) on project quarkus-myfaces-showcase:
[ERROR] The plugin io.quarkus:quarkus-maven-plugin:3.2.9.Final has unmet prerequisites:
[ERROR] Required Java version 17 is not met by current version: 11.0.32

If I use Java 17, then I get:

[ERROR] Failed to execute goal org.apache.felix:maven-bundle-plugin:4.0.0:manifest (bundle-manifest) on project myfaces-api: Execution bundle-manifest of goal org.apache.felix:maven-bundle-plugin:4.0.0:manifest failed.: ConcurrentModificationException -> [Help 1]
[ERROR]

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.

- 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
@tandraschko

Copy link
Copy Markdown
Member

Why the CI on 11 builds then sucessful?

@volosied

Copy link
Copy Markdown
Contributor Author

API/ IMPl still use Java 11:

javap -v ./target/classes/jakarta/faces/convert/ShortConverter.class | grep major
major version: 55

javap -v ./target/classes/org/apache/myfaces/renderkit/html/base/HtmlMessageRendererBase.class | grep major
major version: 55

Quarkus Extension use 17:

javap -v ./quarkus/runtime/target/classes/org/apache/myfaces/core/extensions/quarkus/runtime/exception/QuarkusExceptionHandler.class | grep major
major version: 61

Comment thread impl/pom.xml
</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>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May not be needed anymore. I could remove.

@tandraschko

Copy link
Copy Markdown
Member

CI is working on 11
Both Apache and GitHub

@volosied

Copy link
Copy Markdown
Contributor Author

Don't understand what's going on....? I'm only running mvn clean install.

[ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:3.2.9.Final:build (default) on project quarkus-myfaces-showcase:
[ERROR] The plugin io.quarkus:quarkus-maven-plugin:3.2.9.Final has unmet prerequisites:
[ERROR] Required Java version 17 is not met by current version: 11.0.32

java -version
openjdk version "11.0.32" 2026-07-21
IBM Semeru Runtime Open Edition 11.0.32.0 (build 11.0.32+9)
Eclipse OpenJ9 VM 11.0.32.0 (build 11.0.32+9-openj9-0.60.0, JRE 11 Linux amd64-64-Bit Compressed References 20260728_1803 (JIT enabled, AOT enabled)
OpenJ9 - 396c827fb3
OMR - 2e3166f7a
JCL - cb00718c9b based on jdk-11.0.32+9)

@melloware

Copy link
Copy Markdown
Contributor

yeah 4.0 is Java 11 i thought 4.1 was 17?

@volosied

volosied commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

CI runs mvn clean deploy -Pgenerate-assembly but not mvn clean install

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.

@tandraschko

Copy link
Copy Markdown
Member

4.0 is Java 11
So please create a PR first to change the CI, so we see errors within CI

@melloware

Copy link
Copy Markdown
Contributor

The CI for 4.0.x already runs as 11? See:

- uses: actions/checkout@v3
with:
persist-credentials: false
- name: Set up JDK 11
uses: actions/setup-java@v3
with:
distribution: 'temurin'
java-version: 11

@tandraschko

Copy link
Copy Markdown
Member

I mean the mvn clean Install before the deploy?

@melloware

Copy link
Copy Markdown
Contributor

OK added PR: #1060

@melloware

Copy link
Copy Markdown
Contributor

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

@melloware

Copy link
Copy Markdown
Contributor

ahh it looks like 2.16.12.Final is the last Quarkus to support Java 11.

@melloware

Copy link
Copy Markdown
Contributor

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?

@tandraschko

Copy link
Copy Markdown
Member

No Idea
We have 3 Options:

  • move to java17, spec is java 11
  • release without quarkus
  • move quarkus to a own project

@tandraschko

Copy link
Copy Markdown
Member

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?!

@tandraschko

Copy link
Copy Markdown
Member

Can you add it to your PR @melloware?

@melloware

Copy link
Copy Markdown
Contributor

yep i totally agree @tandraschko fixing my PR now

@melloware

Copy link
Copy Markdown
Contributor

@volosied all fixed! Closing this PR

@melloware melloware closed this Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants