Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Blocker
-
Resolution: Unresolved
-
Affects Version/s: 2.0.3
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Design, Patterns & Best Practices, Plugins and Lifecycle
-
Labels:None
-
Environment:Revision 974 of Cargo (https://svn.codehaus.org/cargo/cargo/trunk/core/api/)
-
Complexity:Intermediate
-
Number of attachments :
Description
In the Clover plugin the report mojo is an aggregator (http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-clover-plugin/src/main/java/org/apache/maven/plugin/clover/CloverReportMojo.java). It also spawns a forked lifecycle:
* @execute phase="test" lifecycle="clover" * @aggregator
When I run this clover report on the Cargo API module, which contains children modules, all the modules are executed several times as shown in the attached logs. They should be executed only once. The @aggregator is supposed to execute only once and it executes several times.
Issue Links
- is related to
-
MJAVADOC-171
Modules in multi-module projects are "built" too often
-
- relates to
-
SUREFIRE-449
In multi-module projects, all tests are run for each module in the module tree
-
-
MJAVADOC-137
javadoc:javadoc always runs as "aggregator"
-