[
https://issues.apache.org/jira/browse/MJAVADOC-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826259#comment-16826259
]
Gordon Pettey edited comment on MJAVADOC-595 at 4/26/19 6:59 PM:
-----------------------------------------------------------------
I think the problem stems from commons-lang3 {{SystemUtils.getJavaHome()}}
usage of {{getProperty("java.home")}} instead of {{getEnv("JAVA_HOME")}}, which
are different (by "/jre") for pre-9 JDKs. The AbstractJavadocMojo code appears
to be a workaround for that.
was (Author: petteyg359):
I think the problem stems from commons-lang3 {{SystemUtils.getJavaHome()}}
usage of {{getProperty("java.home")}} instead of {{getEnv("JAVA_HOME")}}, which
are different (by "/jre") for pre-9 JDKs. The code quoted in the issue
description appears to be a workaround for that.
> javadoc not found using java.home
> ----------------------------------
>
> Key: MJAVADOC-595
> URL: https://issues.apache.org/jira/browse/MJAVADOC-595
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Oliver Lüttin
> Priority: Major
>
> When searching for the javadoc executable the plugin looks in
> java.home/../bin.
> This doesn't work with ubuntu 18.10 and java-11-openjdk.
> Instead it should look at java.hom/bin where the javadoc executable is
> located.
> Here's the code snippet from AbstactJavadocMojo:
> {code:java}
> 3720 private String getJavadocExecutable()
> 3721 throws IOException
> 3722 {
> ...
> 3768 else
> 3769 {
> 3770 javadocExe =
> 3771 new File( SystemUtils.getJavaHome() + File.separator + ".." +
> File.separator + "bin", javadocCommand );
> 3772 }
> {code}
>
> As workaround one could configure the executable in the pom.xml:
>
> {code:java}
> <configuration>
> <javadocExecutable>${java.home}/bin/javadoc</javadocExecutable>
> </configuration>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
