-
-
Notifications
You must be signed in to change notification settings - Fork 301
[Java24] Create new .properties files and compiled class files #6529
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
Conversation
188e057
to
35977ac
Compare
@bjhargrave could you maybe have a look? I tried having a look at past PRs from you, but not sure what I missed. I will squash commits at the end. |
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 think you also should update the CI build to test with JDK 17 (which is the minimum version required), all subsequent LTS versions (21) and also the latest released version (24).
You should also investigate any changes to the JVMS since JDK 17 which may need updates to the biz.aQute.bnd.util/src/aQute/bnd/classfile package.
biz.aQute.bndlib/src/aQute/bnd/build/model/JavaSE_18.properties
Outdated
Show resolved
Hide resolved
ab32c2a
to
9f5bb81
Compare
I checked https://docs.oracle.com/en/java/javase/24/language/java-language-changes-summary.html To me it looks like SealedClasses permanent in Java 17 were the last major JVM change relevant* for bnd. * with 'relevant' I mean mainly things which affect types and packages which are needed to calculate manifest. What is your opinion on Preview features? When would we consider supporting them? @bjhargrave I first thought about Module Import Declarations but I don't think we need to handle them specifically since the byte code still contains |
i am just here to say thank you @chrisrueger |
Your link is to the JLS. I am talking about the JVMS which specifies the class file format: https://docs.oracle.com/javase/specs/jvms/se24/html/jvms-4.html. But it does appear there are no class file format changes since 17. |
5bee245
to
aa84952
Compare
@bjhargrave question to PR #6536 next door where I am experimenting with upgrading to use latest Eclipse 2025-03. I get
i have Would that error go away once this PR here is inside bnd? Are those package bnd/biz.aQute.resolve/src/biz/aQute/resolve/BndrunResolveContext.java Lines 172 to 179 in ff9e429
but wanted to confirm. BTW: Eclipse 2024-12 is running fine. This error starts with 2025-03 |
Probably since Bnd will then know about the new packages added since Java 17. |
- using https://github.com/chrisrueger/jdk-packages and https://github.com/bjhargrave/java-platform-packages e.g. ./download_jdk.sh 24 mac aarch64 ./list_jdk_packages_for_bnd.sh 24 mac aarch64 > "JavaSE_24.properties" - compile classes with newer JDKs up to 24 - Update compilerversions.jar (via bnd buildx compilerversions.bnd) - Update MultiReleaseTest.java - add enums for more future JAVA versions - remove properties for JDK 18,20,23 because packages are equal to the prior version - CI Build: remove deprecated security manager - CI Build: build with LTS JDK 21 and JDK23 - CI Build: JDK 24 will come later as it is not supported by gradle yet (maybe in 8.14) Signed-off-by: Christoph Rueger <[email protected]>
aa84952
to
245fd3e
Compare
Thanks @bjhargrave I squashed all commits now. Would be ready to go then. |
Closes #6531
.properties
files