You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2018/05/21 10:06:00 UTC

[jira] [Closed] (MJAVADOC-522) Javadoc generation broken on JDK 10 (Commons Lang3 gives NullPointerException)

     [ https://issues.apache.org/jira/browse/MJAVADOC-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MJAVADOC-522.
-----------------------------------
    Resolution: Duplicate
      Assignee: Robert Scholte

> Javadoc generation broken on JDK 10 (Commons Lang3 gives NullPointerException)
> ------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-522
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-522
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>          Components: javadoc
>    Affects Versions: 3.0.0
>         Environment:  * JDK 10
>  * Maven 3.5.3
>  * Maven Javadoc plugin 3.0.0
>            Reporter: Daniel Fernández
>            Assignee: Robert Scholte
>            Priority: Major
>
> Executing {{javadoc:javadoc}} in JDK 10 throws a {{NullPointerException}} caused by Apache Commons Lang 3.5:
> {code}
> 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.JavadocReport.generate (JavadocReport.java:134) at org.apache.maven.plugins.javadoc.JavadocReport.doExecute (JavadocReport.java:329) at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute (AbstractJavadocMojo.java:1909) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> ...
> {code}
> The reason for this is [LANG-1365|https://issues.apache.org/jira/browse/LANG-1365] which was fixed in [this commit|https://github.com/apache/commons-lang/commit/a618b844c5a261ced37385ab3947de6e215d46f7].
> Updating to Apache Commons Lang 3.7 should solve the issue.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)