[MJAVADOC-134] Support aggregated reports at each level in the multi-module hierarchy

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 3.1.0
• Assignee: Robert Scholte
• Reporter: skaze
• Created: 17/Jul/07 15:03
• Updated: 16/Jul/21 18:23
• Resolved: 18/Dec/18 22:23

Description

The current system makes the assumption that if one wants aggregated reports one does not want further javadoc reports (aggregated ones) down the hierarchy. We do require this functionality and in fact do the same for all our reports (PMD, Checkstyle, Clover, JXR, Surefire, etc):

A->B->C->D1 (JAR)
A->B->C->D2 (JAR)
A->B->E(JAR)
A->F (JAR)

A - javadoc for D1,D2,E,F
B - javadoc for D1,D2,E
C - javadoc for D1,D2
D1 - javadoc for D1
D2 - javadoc for D2
E - javadoc for E
F - javadoc for F

This way there is the required info at the appropriate level throughout the hierarchy. And nope we dont care about space or generation times

Issue Links

• is duplicated by: MJAVADOC-311 Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level.
• is related to: MJAVADOC-400 aggregate-jar does nothing if called as part of a reactor build