Details
-
Type:
Bug
-
Status:
Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.3
-
Fix Version/s: None
-
Labels:None
-
Environment:Maven 2.0.8, Linux
-
Testcase included:yes
-
Number of attachments :
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
-
- relates to
-
MNG-2184
Possible problem with @aggregator and forked lifecycles
-
-
MJAVADOC-137
javadoc:javadoc always runs as "aggregator"
-
-
MSITE-454
Don't use aggregator mojos for default report set
-
-
MNG-5170
prevent mojo to fork lifecycle when same lifecycle is already executed
-