You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.
I've had the feeling for a long time that the scala-maven-plugin (or something else in the build chain) was doing some strange things. For example, my build on Cloudbees randomly fails and it seems to do so because the underlying JDK is selected randomly (or in a way I fail to understand).
This impression was confirmed recently as Apple (great move, people) decided to force the latest JDK version on everyone:
my project pom declares 1.6 source and target levels
my project indeed displays the JDK6 library
I get some compilation errors in eclipse complaining that some classes extending some Swing classes should be parameterized. Problem is these classes have a type parameter only since... Java 7!
I finally uninstalled JDK7 from my Mac, and the errors magically disappeared
Any idea?
Cheers,
Stéphane
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi David,
I've had the feeling for a long time that the scala-maven-plugin (or something else in the build chain) was doing some strange things. For example, my build on Cloudbees randomly fails and it seems to do so because the underlying JDK is selected randomly (or in a way I fail to understand).
This impression was confirmed recently as Apple (great move, people) decided to force the latest JDK version on everyone:
Any idea?
Cheers,
Stéphane
The text was updated successfully, but these errors were encountered: