[jira] [Commented] (MJAVADOC-595) javadoc not found using java.home

["Curtis Rueden (Jira)" <ji...@apache.org>]

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

Curtis Rueden commented on MJAVADOC-595:
----------------------------------------

It looks like this bug was fixed by:

https://github.com/apache/maven-javadoc-plugin/commit/4bf64b02

So now we just need a 3.2.1 release, no?

> 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
(v8.3.4#803005)