Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
W2K, JDK 6u5, Maven 2.0.8
Description
For the following project design (s. attached testcase):
parent
- library // javadoc:aggregate!
- module-a
- module-b
- application
javadoc report for 'library' is not generated (not invoked), if 'mvn site' is
called at 'parent' level (but is properly done if run at 'library' level itself).
Attachments
Attachments
Issue Links
- is related to
-
MJAVADOC-179 Aggregate report ignores sourcepath customization of subprojects
- Closed
-
MJAVADOC-97 enable internal/external dependency references as links
- Closed
- is superceded by
-
MJAVADOC-311 Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level.
- Closed
- relates to
-
MJAVADOC-284 detectOfflineLinks sets off extra spurious executions of javadoc
- Closed