-
Notifications
You must be signed in to change notification settings - Fork 87
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
Find out what we can do to release for jdk6 instead of jdk7 #77
Comments
We'll have the same issue for all modules, so let's consolidate the discussion here. cc @ashawley @gourlaysama @Sciss @xuwei-k @SethTisue @retronym It's no longer possible to publish to sonatype when running on Java 6, see here, as @MasseGuillaume noted in this commit: f43e772. In general, we'd like to build releses of Scala modules for Scala 2.11 on Java 6 to make sure the generated artifacts don't have accidental dependencies on Java APIs that don't exist in Java 6. A famous case was To minimize the risk, we could run the 2.11 build on both Java 6 and 8 for CI validation, but use only 8 for publishing. This would prevent direct use of APIs that don't exist on Java 6. There's still a risk for cases like the extension method above, but it's a small one. In order to be really sure, we could compare the classfiles built on 6 and 8 during CI validation, they should be identical. |
It's not going to be as thorough as comparing the |
Can we just run with SBT with Java 8 (or later), and set That ought to use Java 6's classpath for |
Good point to switch the JVM. Maybe it's easy to switch to 8 for the publish-signed step, for example with a |
Run sbt with jdk8 and test with the jdk from the build matrix (fix #77)
No description provided.
The text was updated successfully, but these errors were encountered: