-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[#] JDK 25 support (multiple JIRA) #1533
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
base: main
Are you sure you want to change the base?
Conversation
| parameters { | ||
| choice(name: 'nodeLabel', choices: ['ubuntu', 's390x', 'arm', 'Windows']) | ||
| choice(name: 'jdkVersion', choices: ['jdk_17_latest', 'jdk_21_latest', 'jdk_24_latest', 'jdk_17_latest_windows', 'jdk_21_latest_windows', 'jdk_24_latest_windows']) | ||
| choice(name: 'jdkVersion', choices: ['jdk_17_latest', 'jdk_21_latest', 'jdk_25_latest', 'jdk_17_latest_windows', 'jdk_21_latest_windows', 'jdk_25_latest_windows']) |
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.
I guess we should remove jdk_17 there already.
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.
JDK 17 should stay. The new change is during release builds we need to ensure JDK 21 is used to support the multi-release jar working. The other PR has the enforce plugin set to check for JDK 21 being used only during release.
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.
It does, but at least at present this PR should also be updating it to require at least 24 (I just went with requiring 25 for Artemis, sets the 25 baseline now and saves changing it later, plus who really needs to use 24 for releasing now) since thats the compilation level being used.
|
Jenkins test setup output |
activemq-broker/src/main/java24/org/apache/activemq/broker/jmx/SubjectShim.java
Outdated
Show resolved
Hide resolved
|
Looking at the Jenkins build https://ci-builds.apache.org/job/ActiveMQ/job/ActiveMQ/view/change-requests/job/PR-1533/6/cloudbees-pipeline-explorer/?filter=131 - it looks like the tests run using JDK17. Am I reading that correctly? Could we get a run with JDK25? |
… test to remove SecurityManager Co-authored-by: Gurpartap Singh <gurpartap0306>
…Test.java (cherry picked from commit 07f1a3f23b46f27d2e460b7b6bb88fb9ee9485c8)
ffdcb1c to
29bef28
Compare
Apache Jenkins JDK 25 test passed except for two tests
TODO:
ref: https://ci-builds.apache.org/job/ActiveMQ/job/ActiveMQ/job/PR-1533/6/