[MNG-2184] Possible problem with @aggregator and forked lifecycles

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.3
• Fix Version/s: Issues to be reviewed for 4.x
• Component/s: Design, Patterns & Best Practices, Plugins and Lifecycle
• Environment: Revision 974 of Cargo (https://svn.codehaus.org/cargo/cargo/trunk/core/api/)
• Assignee: Unassigned
• Reporter: Vincent Massol
• Created: 28/Mar/06 11:15
• Updated: 31/Dec/23 10:36

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 contained by: MNG-7991 refactor "aggregator" goal feature
• is related to: MJAVADOC-171 Modules in multi-module projects are "built" too often
• is related to: MSITE-454 Don't use aggregator mojos for default report set
• relates to: SUREFIRE-449 In multi-module projects, all tests are run for each module in the module tree
• relates to: MJAVADOC-137 javadoc:javadoc always runs as "aggregator"
• relates to: SUREFIRE-905 Surefire report plugin only executed tests once. Junit Categorization is not possible
• relates to: MNG-5170 prevent mojo to fork lifecycle when same lifecycle is already executed