[MJAVADOC-400] aggregate-jar does nothing if called as part of a reactor build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 2.9.1
• Environment: Reproduced with Oracle Java 1.7.0_45, Maven 3.0.5. Also reproduced with Maven 3.2.2.
• Assignee: Robert Scholte
• Reporter: Philip Aston
• Created: 07/Jul/14 16:13
• Updated: 02/May/21 18:33
• Resolved: 02/May/21 18:33

Description

The attached reproduction.tgz contains a multi-module project com.repo:parent, and two child modules, com.repo:module_a and com.repo:module_b. com.repo:module-a is a jar module that contains a Java class. com.repo:module-b depends on com.repo:module-a and has uses javadoc:aggregate-jar to create a javadoc attachment.

If I change into the module_b directory and run mvn clean install, a com.repo:module-b:javadoc attachment is not created.

However, if I run mvn clean install from the top level, a com.repo:module-b:javadoc attachment is not created. I believe this to be a bug.

Running with -X shows that the aggregate-jar mojo is configured, but never executed.

If I change to module-b and run with -X, I see an MultipleArtifactsNotFoundException, but it otherwise behaves as I would expect. This looks similar to the symptoms of MVN-4618.

Issue Links

• relates to: MJAVADOC-134 Support aggregated reports at each level in the multi-module hierarchy
• relates to: MJAVADOC-311 Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level.