[MJAVADOC-311] Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level.

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.7
• Environment: Windows Vista x64, JDK 6u22, Maven 3.0
• Assignee: Robert Scholte
• Reporter: André Fügenschuh
• Created: 26/Oct/10 06:45
• Updated: 18/Dec/18 22:43
• Resolved: 18/Dec/18 22:43

Description

With a multi-module project design (cf. attached testcase):

- parent        (pom)
  + library     (pom)  // javadoc:aggregate
    + module-a  (jar)
    + module-b  (jar)
  + application (jar)  // javadoc:javadoc

run
mvn site | mvn -DstagingDirectory=[dir] site:stage
at parent level.

Result:
Aggregated javadocs for library are not generated (but are properly done if mvn site is run at library level itself), while javadocs at application level are generated.

OT: as appropriate <modules> sections are declared (cf. attached testcase), mvn compile runs as expected at parent level.

This is a follow-up to MJAVADOC-181, which, although marked as resolved, has never been working for me using the old site/reports configuration for Maven 2.2.1 / Site plugin 2.1.1.

Issue Links

• duplicates: MJAVADOC-134 Support aggregated reports at each level in the multi-module hierarchy
• is related to: MJAVADOC-400 aggregate-jar does nothing if called as part of a reactor build
• supercedes: MJAVADOC-181 Javadoc report not generated for multi-module project if run from parent level.