[
https://issues.apache.org/jira/browse/MJAVADOC-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193638#comment-17193638
]
Benjamin Marwell commented on MJAVADOC-650:
-------------------------------------------
Hello [~evanward], I never set my {{JAVA_HOME}} to anything else than the root
directory (i.e. {{$JAVA_HOME/jre/..}}). This never failed me and I have active
Java8 and java 11 jdks working this way. In fact, jabba (above output) works
this way. Therefore, your first claim is just untrue – no JDK changed the path
of the javadoc binary. I am on Linux btw.
Which JDK are you using? A JDK which is shipped with Ubuntu or Debian? If so,
they may have changed something.
Also, which Maven installation are you using? A maven installation which is
being shipped with debian? Your link to a Debian-specific fix suggests this,
and this would not be the place to fix this.
But, I am interested if this is a Debian-Specific issue or not. I can only tell
you, a {{$JAVA_HOME/jre/bin/javadoc}} binary should never have existed.
> Fix Javadoc search path for Java 9+
> -----------------------------------
>
> Key: MJAVADOC-650
> URL: https://issues.apache.org/jira/browse/MJAVADOC-650
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Evan Ward
> Priority: Major
>
> Hi,
> Java 9 changed the directory structure of the JDK and JRE so [1] no longer
> finds the javadoc command. Debian has a patch to fix this at [2]. It's only a
> few lines. Please apply the patch or implement the capability to look for
> `./bin/javadoc` as well as `../bin/javadoc`.
> Thanks,
> Evan
>
> [1]
> [https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L3805]
> [2]
> [https://sources.debian.org/data/main/m/maven-javadoc-plugin/3.0.1-3/debian/patches/openjdk-9-javadoc-path.patch]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
