-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test with Java 21 and modernization #105
Conversation
General error during conversion: Unsupported class file major version 65
This version of maven-hpi-plugin requires Jenkins 2.361 or later
This version of maven-hpi-plugin requires Jenkins 2.361 or later
We're still using JDK8, and that's why the build is failing. |
Thanks, Basil. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs the correct 2.361.x plugin bom release number.
Of course, sorry about that. |
Co-authored-by: Mark Waite <[email protected]>
@car-roll , @rsandell , or @dwnusbaum could you merge this so that the plugin is regularly tested with Java 21 and Java 17? |
Thanks @car-roll ! |
Test with Java 21
Java 21 was released Sep 19, 2023. We want to announce full support for Java 21 in early October and would like the most used plugins to be compiled and tested with Java 21.
The acceptance test harness and plugin bill of materials tests are already passing with Java 21. This is a further step to improve plugin readiness for use with Java 21 and for development with Java 21.
The change intentionally tests only two Java configurations, Java 17 and Java 21 because we believe that the risk of a regression that only affects Java 11 is shallow. We generate Java 11 byte code with the Java 17 and the Java 21 builds, so we're already testing Java 11 byte code.
Testing done
Confirmed tests pass with Java 21 after upgrading to a recent parent POM and to Jenkins version 2.361.4 as the minimum version.