[MJAVADOC-171] Modules in multi-module projects are "built" too often

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3
• Environment: Maven 2.0.8, Linux
• Assignee: Herve Boutemy
• Reporter: Stefan Seidel
• Created: 01/Feb/08 04:26
• Updated: 06/Apr/15 01:36
• Resolved: 11/May/14 10:57

Description

In a multi-module project, all modules are "built" twice for each module. This leads to huge performance problems when many modules are in a project. In the attached sample project, the xmlbeans plugin is executed 27 times for a project with one parent module and two submodules. 18 of these executions can be attributed to the javadoc plugin. With version 2.2, only 3 invocations (once for each project) are caused by the javadoc plugin.

Issue Links

• is related to: SUREFIRE-449 In multi-module projects, all tests are run for each module in the module tree
• is related to: MSHARED-266 run aggregator reports only when current projet is pom packaging and has modules
• is related to: MSHARED-333 display what phase or goal is forked by a report
• relates to: MNG-2184 Possible problem with @aggregator and forked lifecycles
• relates to: MJAVADOC-137 javadoc:javadoc always runs as "aggregator"
• relates to: MSITE-454 Don't use aggregator mojos for default report set
• relates to: MNG-5170 prevent mojo to fork lifecycle when same lifecycle is already executed