[
https://issues.apache.org/jira/browse/MJAVADOC-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038528#comment-15038528
]
ASF GitHub Bot commented on MJAVADOC-437:
-----------------------------------------
GitHub user hwellmann opened a pull request:
https://github.com/apache/maven-plugins/pull/72
[MJAVADOC-437] javadoc:aggregate fails on initial build
For aggregate reports, do not resolve artifacts of current reactor to make
initial build pass.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hwellmann/maven-plugins MJAVADOC-437
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-plugins/pull/72.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #72
----
commit 2d10bff932a39278beafac5235c028cecb0fecba
Author: Harald Wellmann <[email protected]>
Date: 2015-12-03T20:08:56Z
[MJAVADOC-437] for aggregate reports, do not resolve artifacts of
current reactor to make initial build pass
----
> 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
>
> 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)
