maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Young (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJAVADOC-517) NPE under Java 10 RC
Date Thu, 08 Mar 2018 11:28:00 GMT

    [ https://issues.apache.org/jira/browse/MJAVADOC-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391103#comment-16391103
] 

Ian Young commented on MJAVADOC-517:
------------------------------------

Incidentally, {{commons-lang3}} seems to have a bug relative to functioning under Java 11
EA even in commons-lang 3.7, so this will come up again in the next few months. I raised a
ticket there: https://issues.apache.org/jira/browse/LANG-1384

> 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
>            Priority: Major
>
> 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)

Mime
View raw message