maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gordon Pettey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJAVADOC-595) javadoc not found using java.home
Date Thu, 25 Apr 2019 17:30:00 GMT

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

Gordon Pettey commented on MJAVADOC-595:
----------------------------------------

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)

Mime
View raw message