Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0.3
-
None
-
Revision 974 of Cargo (https://svn.codehaus.org/cargo/cargo/trunk/core/api/)
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.
Attachments
Attachments
Issue Links
- Is contained by
-
MNG-7991 refactor "aggregator" goal feature
- Open
- is related to
-
MJAVADOC-171 Modules in multi-module projects are "built" too often
- Closed
-
MSITE-454 Don't use aggregator mojos for default report set
- Closed
- relates to
-
SUREFIRE-449 In multi-module projects, all tests are run for each module in the module tree
- Closed
-
MJAVADOC-137 javadoc:javadoc always runs as "aggregator"
- Closed
-
SUREFIRE-905 Surefire report plugin only executed tests once. Junit Categorization is not possible
- Closed
-
MNG-5170 prevent mojo to fork lifecycle when same lifecycle is already executed
- Closed