maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MNG-2184) Possible problem with @aggregator and forked lifecycles
Date Thu, 30 Mar 2006 16:38:44 GMT
     [ http://jira.codehaus.org/browse/MNG-2184?page=all ]

Vincent Massol updated MNG-2184:
--------------------------------

    Priority: Blocker  (was: Major)

Moving to blocker as the clover plugin cannot be released before this is fixed

> Possible problem with @aggregator and forked lifecycles
> -------------------------------------------------------
>
>          Key: MNG-2184
>          URL: http://jira.codehaus.org/browse/MNG-2184
>      Project: Maven 2
>         Type: Bug

>   Components: Plugins and Lifecycle
>     Versions: 2.0.3
>  Environment: Revision 974 of Cargo (https://svn.codehaus.org/cargo/cargo/trunk/core/api/)
>     Reporter: Vincent Massol
>     Priority: Blocker
>  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


Mime
View raw message