-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add support for Java 11 and test with Maven 3.6.0 #63
Conversation
We also hit it in the Jenkins project: https://issues.jenkins-ci.org/browse/JENKINS-54843 (CC @batmat @alecharp). I can workaround it there, but a release would be nice |
@@ -84,6 +84,9 @@ | |||
// Java10 | |||
JDK_TO_MAJOR_VERSION_NUMBER_MAPPING.put( "1.10", 54 ); | |||
JDK_TO_MAJOR_VERSION_NUMBER_MAPPING.put( "10", 54 ); | |||
|
|||
// Java11 | |||
JDK_TO_MAJOR_VERSION_NUMBER_MAPPING.put( "11", 55 ); |
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.
Makes sense to put Java 12 as well. It is already in early access
FTR, I've assigned this to myself to get it over the fence. Also just started a vote on the mojohaus-dev ML to release mojo-parent:50, which I plan to use in a followup to bump to Java 7 minimum (once/if the vote passes). I've no idea how AppVeyor is supposed to run/check things here. Apparently, there's been no PR build from this service, for some reason. Also going to do small adjustments. |
This fails with JDK11. Checking this in to see if I can get a green PR build without this.
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.
LGTM, moving forward.
Fixes #61
Travis CI tests with cobertura reports failed with Java 11 due to not existing tools.jar - probably this plugin should be excluded from the build.