-
Notifications
You must be signed in to change notification settings - Fork 445
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
Has Java 7 happened already? #416
Comments
Bumped to Java 7 as the native packager 1.0.0-M2 requires us to unfortunately. Perhaps this can revert back. There is an associated issue: sbt/sbt-native-packager#416
Nothing i know of. Travis should have failed. However your logs show something different :/ |
Can you try |
@huntc is this issue still present? |
Just tested with |
Ah, my bad, I was using java 1.7. Anyhow, if you're still testing on 1.6 and all is well then we'll leave it as my issue to resolve I think. |
I'm so dumb. :-P So it turns out that the bytecode in my plugin was targeting 1.7. So sorry for the noise. All is well with the native packager here. |
Nevermind ❤️ |
I'm not entirely sure what's going on, but if I use
1.0.0-M2
then Java 7 is expected. I'm wondering if some Java 7 transitive dependencies have been brought in...I don't believe we're making the Java 7 leap until sbt goes 1.0.0.
Here's the full console output from a scripted session on
sbt-bundle
. If I run via Java 7 then all is well (incidentally this is strange as I see you have an openjdk 6 test for travis):The text was updated successfully, but these errors were encountered: