[
https://issues.apache.org/jira/browse/MJAVADOC-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407619#comment-16407619
]
Giovanni Lovato commented on MJAVADOC-517:
------------------------------------------
Which repository should I use to test 3.0.1? At
[https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-javadoc-plugin/3.0.1-SNAPSHOT/]
there are old snapshots.
> NPE under Java 10 RC
> --------------------
>
> Key: MJAVADOC-517
> URL: https://issues.apache.org/jira/browse/MJAVADOC-517
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Ian Young
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.0.1
>
>
> Under Java 10 RC, the plugin generates the following exception:
> {code:java}
> Caused by: java.lang.NullPointerException
> at org.apache.commons.lang3.SystemUtils.isJavaVersionAtLeast
> (SystemUtils.java:1626)
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getJavadocExecutable
> (AbstractJavadocMojo.java:3683)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
> (AbstractJavadocMojo.java:2001)
> at org.apache.maven.plugins.javadoc.JavadocJar.doExecute
> (JavadocJar.java:190)
> {code}
> This seems to be down to the version string:
> {code:java}
> java version "10" 2018-03-20
> Java(TM) SE Runtime Environment 18.3 (build 10+43)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+43, mixed mode)
> {code}
> {{commons-lang3}} version 3.5 can't deal with this, see
> https://issues.apache.org/jira/browse/LANG-1365
> Inserting an explicit dependency on {{commons-lang3}} version 3.7 for the
> plugin works round the issue, and changing the dependency seems like the
> right fix for the next release of this plugin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
