[
https://issues.apache.org/jira/browse/MJAVADOC-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193607#comment-17193607
]
Evan Ward commented on MJAVADOC-650:
------------------------------------
Hi [~bmarwell],
The `javadoc` executable has stayed in the same place. The change was that
`"java.home"` changed from `/usr/lib/jvm/java-8-openjdk-amd64/jre/` to
`/usr/lib/jvm/java-11-openjdk-amd64/. So when the code at the linked line tries
to do `${java.home}/../bin/javadoc` it ends up outside the JDK. The correct
path should be `${java.home}/bin/javadoc` on Java 1.9+ as in the patch from
Debian. It is my understanding that this was an upstream change made by Java,
not Debian specific.
Note that if you're using a Mac and Java >= 1.7 you won't see this bug because
of the if clause above the linked line.
> 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)
