[MJAVADOC-437] javadoc:aggregate fails on initial build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10.3
• Fix Version/s: 2.10.4
• Assignee: Michael Osipov
• Reporter: Harald Wellmann
• Created: 03/Dec/15 19:59
• Updated: 09/Apr/22 12:34
• Resolved: 07/Dec/15 18:28

Description

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).

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.

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.)

Issue Links

• is duplicated by: MJAVADOC-116 Impossible to aggregate javadoc if snapshot never built
• is duplicated by: MJAVADOC-345 Javadoc-aggregate fail
• is duplicated by: MJAVADOC-362 aggregate-jar: javadoc build on multi-module maven project in parent pom does not aggreate classpath
• is related to: MJAVADOC-116 Impossible to aggregate javadoc if snapshot never built
• links to: GitHub Pull Request #132