[
https://issues.apache.org/jira/browse/MNG-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MNG-2184:
--------------------------------------
Priority: Major (was: Blocker)
> Possible problem with @aggregator and forked lifecycles
> -------------------------------------------------------
>
> Key: MNG-2184
> URL: https://issues.apache.org/jira/browse/MNG-2184
> Project: Maven
> Issue Type: Bug
> Components: Design, Patterns & Best Practices, Plugins and
> Lifecycle
> Affects Versions: 2.0.3
> Environment: Revision 974 of Cargo
> (https://svn.codehaus.org/cargo/cargo/trunk/core/api/)
> Reporter: Vincent Massol
> Assignee: John Casey
> Priority: Major
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: cargo.log
>
>
> 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:
> {code}
> * @execute phase="test" lifecycle="clover"
> * @aggregator
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
