[
https://issues.apache.org/jira/browse/JCLOUDS-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825191#comment-16825191
]
ASF subversion and git services commented on JCLOUDS-1496:
----------------------------------------------------------
Commit d51d6e44bcd9936f753b87a6407d5394279347e7 in jclouds's branch
refs/heads/master from Olaf Flebbe
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=d51d6e4 ]
JCLOUDS-1496: Update maven-compiler-plugin for increased JDK compatibility (#25)
* JCLOUDS-1496: Update maven-compiler-plugin for increased JDK compatibility
* increase maven-compiler-plugin version
* A space change to trigger jenkins again
* Another space change to trigger jenkins again
> Update maven-compiler-plugin for increased JDK compatibility
> -------------------------------------------------------------
>
> Key: JCLOUDS-1496
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1496
> Project: jclouds
> Issue Type: Task
> Reporter: Olaf Flebbe
> Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> The maven-compiler-plugin is referenced in the wrong clause of the pom file.
> It should be within <project><build><pluginManagement><plugins>.
> (See for instance
> https://maven.apache.org/plugins/maven-compiler-plugin/usage.html )
> Otherwise you will see Nullptr Exceptions for instance with JDK11.
> For now I propose to only move the plugin and use current version 3.8.0.
> Increasing the errorprone module version will trigger a lot of diagnostics in
> errorprone plugins, which should be dealt seperately.
> Doublechecked: Still compiles with java 1.8
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
