Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level. -------------------------------------------------------------------------------------------------------
Key: MSITE-518 URL: http://jira.codehaus.org/browse/MSITE-518 Project: Maven 2.x Site Plugin Issue Type: Bug Components: inheritance, multi module Affects Versions: 3.0-beta-3 Environment: Windows Vista x64, JDK 6u22, Maven 3.0 Reporter: André Fügenschuh Attachments: maven3-site-javadoc-testcase.zip With a +multi-module project design+ (cf. attached testcase): {noformat} - parent (pom) + library (pom) // javadoc:aggregate + module-a (jar) + module-b (jar) + application (jar) // javadoc:javadoc {noformat} 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira