-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
tree-wide: migrate Java packages to JDK 21 #25127
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
tree-wide: migrate Java packages to JDK 21 #25127
Conversation
|
a5e6249
to
ad82097
Compare
Working on Termux after using
ant test log
apksigner test log
bdsup2sub test logI found out that
d8 test log
dex2jar test log
gradle test log
groovy test log
jython test log
kotlin test log
maven test log
pdftk test log
procyon-decompiler test log
scala test log
|
ad82097
to
c8408ff
Compare
agnostic-apollo, because you explained in 2024 that at the time, many things still depended on
Here is a recap of what has changed since then:
Here is a recap of what this new PR would do:
|
- Fixes termux#25027 - JDK 21 has been released for a year, so theoretically, all packages should be ready now, but it will be necessary to test each package's basic functionality with `openjdk-21` installed, to make sure that they are compatible. - Now that termux#25214 has been merged, it should be easier for termux-apt users whose `java` command is set to `openjdk-17`, to get it automatically updated to `openjdk-21` without necessarily having to uninstall `openjdk-17`.
c8408ff
to
cd41992
Compare
I will merge this in 24 hours if no problems are found. |
- Unfortunately, during the development of #25127, `libcommons-lang3-java` was auto-updated to the same version as in my branch, and when I rebased and merged my branch, the automerge automerged the two bumps into the same version, but this has unfortunately prevented the change of dependency of `libcommons-lang3-java` from `openjdk-17` to `openjdk-21` from deploying into the mirror.
- Unfortunately, during the development of termux/termux-packages#25127, `libcommons-lang3-java` was auto-updated to the same version as in my branch, and when I rebased and merged my branch, the automerge automerged the two bumps into the same version, but this has unfortunately prevented the change of dependency of `libcommons-lang3-java` from `openjdk-17` to `openjdk-21` from deploying into the mirror.
While there will be more JDK LTS in the future, does it means that we need to adapt some virtual package like |
It is assumed that currently most people will want OpenJDK 21, but OpenJDK 17 is still possible to install and switch to using |
Fixes Termux Maven Tied to Java-17 #25027
JDK 21 has been released for a year, so theoretically, all packages should be ready now, but it will be necessary to test each package's basic functionality with
openjdk-21
installed, to make sure that they are compatible.Now that fix(main/openjdk-{17,21}): adopt '.alternatives' system #25214 has been merged, it should be easier for termux-apt users whose
java
command is set toopenjdk-17
, to get it automatically updated toopenjdk-21
without necessarily having to uninstallopenjdk-17
.