-
Notifications
You must be signed in to change notification settings - Fork 180
[EXPERIMENT] test with java 24 #1534
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
running into Java deprecations for methods on 'Unsafe' class
|
We need later move to Java 11 and migrate some code to VarHandle I think, as Java 25 is coming next year, which is a LTS version. |
The biggest issue is having our builds fail if we use any deprecated code. Scala 2.13.15 upgrade is blocked for similar reasons. |
How about add |
We have to support 3 Scala versions and the deprecation warnings are different on them. Add extra nowarn annotations and they can fix one build but break another. |
I'm working on this, I think we should test the latest JDK too. |
@pjfanning 3.3.5-RC3 is released. |
@pjfanning how about update this pr to make it test JDK23, it should be ok now. |
We can now test with JDK 24. |
Scala 2.12.20 does not properly support Java 24
|
@SethTisue Is there any update for next 2.12.x for JDK 24? |
@SethTisue If you cut a new Scala 2.12.x release, it would be great if that would also already unlock Java 25 by upgrading asm (I hope they cut a new release soon) - so we can test early with latest ea builds already (since it's the next LTS) : |
Scala 2.13.16 run went ok - some test failures due to TLS changes in Java 24. Some TLS protocols or cipher suites have been removed. Scala 3.3.5 run failed with:
|
@mkurz @He-Pin you can state your case over at https://contributors.scala-lang.org/t/scala-2-12-21-release-planning/6753 |
@pjfanning @raboof Wdyt about it, should we run a nightly test with JDK24? |
Are the failures in this branch now resolved? If so might be nice (though perhaps we should move some of those to weekly rather than nightly?) |
we also hit issues with TLS ciphers that are no longer supported
|
temporary test run but may be refactored later to run nightly