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

Michael Osipov commented on MJAVADOC-437:
-----------------------------------------

Interesting to say that w/o your patch the plugin says:

{noformat}
[WARNING] The dependency: 
[org.apache.maven.plugins.maven-javadoc-plugin.it:mjavadoc437-module1:jar:1.0-SNAPSHOT]
 can't be resolved but has been found in the reactor (probably snapshots).
This dependency has been excluded from the Javadoc classpath. You should rerun 
javadoc after executing mvn install.
[WARNING] IGNORED to add some artifacts in the classpath. See above.
{noformat}

> 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
>             Fix For: 2.10.4
>
>
> 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)

Reply via email to