-
Notifications
You must be signed in to change notification settings - Fork 682
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
Does play 1 support java 9? #1200
Comments
Hi Aleksei!
I didn't even try yet. I cannot even run unit-tests in my current project
with Java9, so I am skeptical about that.
Did you try to run Play application with Java 9?
Andrei Solntsev
2017-10-22 21:27 GMT+03:00 Aleksei Sotnikov <[email protected]>:
… —
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1200>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARE3UqbmDDX7F3Lxrx1qwz4mZCJ2Otaks5su4kXgaJpZM4QCDQX>
.
|
Got it. No, I didn't. I just decided to ask first. |
It appears that Play 1 does not currently support Java 9. At the very least, ApplicationCompiler.java will need to be updated to support the new version. |
I'm getting the following error with continuations on Java 9 which might be related to the above point about ApplicationCompiler and/or JavaFlow...
|
Hi, I have the same errors on calls to I have this warning on application start with JDK 9, but do not know if this is related :
|
fix(tests): issue #1200, added testing compatibility for jdk9+
… jdk9+ refactor(tests): issue playframework#1200, adds Controller.test class and unit test for modification on this issue fix(tests): issue playframework#1200, fixes missing imports fix(tests): issue playframework#1200, fixes encapsulation fix(tests): issue playframework#1200 sorted import errors style(tests): issue playframework#1200 beautification
fix(tests): issue #1200, added testing compatibility for jdk9+
Since this issue was resolved last year I think it should be closed ! |
No description provided.
The text was updated successfully, but these errors were encountered: