-
Notifications
You must be signed in to change notification settings - Fork 9
Travis-CI: test on JDK 11, too #41
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
@SethTisue Thanks for this PR. This looks like a good way forward. I have found the fix needed for jdk11 and started a PR - #42
The second part could be related to the first. I have the following in the build. This too on JVM. Edit: the WARNING below has been fixed in
|
The "illegal reflective access" warnings you can ignore (probably they are already fixed in sbt 1.3.0-RC3?). I don't have any insight into the Scala Native thing. Perhaps it would better to redo the CI matrix so that the Scala Native part of the build stays JDK 8 only for now. |
I'm not sure of the source, but Scala Native is not cooperating now. scala-native/scala-native#1675 |
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.
On this line 1c4e0ad#diff-354f30a63fb0907d4ad57269548329e3R31 we could avoid Native testing by changing +test
to +sconfigJVM/test +sconfigJS/test
. Edit: forget second +
sign.
can you take this PR over? feel free to force-push your own stuff, or just close it and make a new one |
@SethTisue I really appreciate the thought you put into it. Pretty sure we will have jdk11 support shortly thanks to your effort and prodding. |
Continued here: #43 |
in the Scala 2.13 community build, I'm seeing JDK 11 only test failures
I think they'll show up here as well, with this Travis-CI config change