[
https://issues.apache.org/jira/browse/MJAVADOC-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043502#comment-15043502
]
Michael Osipov commented on MJAVADOC-437:
-----------------------------------------
Harald, just checked the interation test. Either I did not understand the issue
properly or the IT code does not fit. To rephrase the problem: if you have
Javadoc in module Bar which refers to classes in module Foo and the snapshots
have never been installed before, Javadoc generation fails due to missing
classpath reactor artifacts. So why do you depend on JUnit which you don't even
use and have Commons IO which is not a reactor dependency? The rest is
commented in line.
> javadoc:aggregate fails on initial build
> ----------------------------------------
>
> Key: MJAVADOC-437
> URL: https://issues.apache.org/jira/browse/MJAVADOC-437
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.10.3
> Reporter: Harald Wellmann
> Assignee: Michael Osipov
>
> h3. Scenario
> Take a SNAPSHOT version of a reactor project with at least two JAR modules.
> Assume that no artifacts of the given SNAPSHOT version have been built before
> (this is usually the case just after running release:perform).
> h3. Actual Behaviour
> Now run {{mvn javadoc:aggregate}}. This build fails in the forked lifecycle.
> maven-javadoc-plugin unnecessarily tries to resolve the JAR artifacts of the
> current reactor (which are not avialable yet) and add them to the Javadoc
> classpath.
> h3. Expected Behaviour
> Aggregated Javadoc should be generated without problems. It is sufficient to
> take the sources of the current reactor and only put *external* dependencies
> on the Javadoc classpath.
> This is a duplicate of an 8 year old bug MJAVADOC-116 with 51 votes which has
> been closed without being fixed.
> A patch for this problem was submitted in MJAVADOC-362, but does not seem to
> have received attention by committers. (I admit the problem description is
> not very clear.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
