[jira] Commented: (MNG-2184) Possible problem with @aggregator and forked lifecycles

["John Casey (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122850 ] 

John Casey commented on MNG-2184:
---------------------------------

See revId: 619720 on trunk...does this do enough to prevent bound-aggregator weirdness?

> Possible problem with @aggregator and forked lifecycles
> -------------------------------------------------------
>
>                 Key: MNG-2184
>                 URL: http://jira.codehaus.org/browse/MNG-2184
>             Project: Maven 2
>          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: Blocker
>             Fix For: 2.1
>
>         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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira