-
Notifications
You must be signed in to change notification settings - Fork 634
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
JDK16 compatibility issues #3284
Comments
I know that cassandra just "recently" supports java 11 in new 4.x version (currently 4.0-RC2). I think lagom uses in development mode cassandra 3.x which is not working on jdk 11 and should not work on 16 either |
That's great observation, I wasn't sure if it's vanilla Cassandra or embedded C* or embedded Kafka. There was also conversation in extracting this part of the maven lifecycle to use testcontainers. |
A lagom build runs tests in both JDK8 and JDK11. A user with JDK11 can develop lagom services and user lagom's |
JDK 16 is not LTS so it's not on the roadmap to support it. Supporting JDK17, OTOH is another matter. At the moment, lagom doesn't support JDK17 because play doesn't support it either. When that happens, the most likely suggestion would be to not use the embedded Cassandra in dev mode ( aka |
For what it’s worth, I’ve found that it’s the Cassandra driver using good old reflection that newer Java versions no longer support unless you explicitly enable via |
Are you looking for help?
Checking if it's possible to migrate development on JDK16
Lagom Version (1.2.x / 1.3.x / etc)
1.6.5
API (Scala / Java / Neither / Both)
Java/maven
Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)
MacOS Big Sur
JDK (Oracle 1.8.0_112, OpenJDK 1.8.x, Azul Zing)
16.0.1.hs-adpt
Library Dependencies
Expected Behavior
Please describe the expected behavior of the issue, starting from the first action.
mvn clean install
Actual Behavior
Project passes but stops when integration suite kicks off.
The text was updated successfully, but these errors were encountered: