-
Notifications
You must be signed in to change notification settings - Fork 180
[EXPERIMENT] try Java 25-ea #1887
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
Cool, we should make 2.0.0 release jdk25 ready. |
Java 25 officially released: https://mail.openjdk.org/pipermail/announce/2025-September/000360.html |
That would be great 👍🏻 |
The open issues are at https://github.com/apache/pekko/issues?q=state%3Aopen%20label%3Ajava24%2F25 The TLDR is that Java 24 and 25 compilers seem to compile Pekko code but it doesn't work as normal at runtime. If we build Pekko with an older Java compiler (eg Java 17), the compiled classes work at runtime with Java 24 and 25 - as far as I can see. If anyone has time to investigate why the Java compiler is behaving like this, feel free to take this on - it would be very useful. |
it should be -release 17 |
We have flags like that in the build but still we end up with invalid classes that cause pattern matching issues (as far as I recall). |
with Java 25-ea (GitHub CI does seem to have a Temurin distro for Java 25 yet), we get Scala code gen issues (similar issues in pekko-http build).
|
Should we retry this? |
#1998 still seems to be an issue - 44 tests failed for pekko-remote with Artery in latest run here. |
relates to #1534