-
Notifications
You must be signed in to change notification settings - Fork 92
tests no longer compile/run on Java 6 #168
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
Comments
(I've heard that Java 9 adds a |
Bleh, well that's good dbuild caught it. Looks like Travis failed to switch to openjdk6, but silently kept going:
Looks like this is a new issue when the Ubuntu build infrastructure was upgraded from precise to trusty. |
Ripping out the Base64 code revealed another issue, which is that org.apache.commons.commons-lang3 is Java 7 as well. Might be able to use an earlier version. |
And now a third issue which is that Scala.js test suite fails in Java 6. We updated the scalajs plugin from 0.6.16 to 0.6.20 in 25c7dc3, and that seems to be the breaking change. Might this be fixed in the next release of Scala.js in scala-js/scala-js#3128
|
I've fixed the meta-issue with Travis and the three issues with Java 6. This should have fixed community-build for Scala 2.11 |
let's see: https://scala-ci.typesafe.com/view/scala-2.11.x/job/scala-2.11.x-integrate-community-build/824/consoleFull (404 til Jenkins gets out of bed and does 100 pushups while repeating his personal daily affirmations under his breath) |
|
#166 adds references to
java.util.Base64
to jvm/src/test, but that's Java 8 API, doesn't exist on Java 6 or 7which also raises a meta-issue: why didn't Travis-CI catch it?
caught by the Scala community build, at e.g. https://scala-ci.typesafe.com/view/scala-2.11.x/job/scala-2.11.x-integrate-community-build/822/
The text was updated successfully, but these errors were encountered: