maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <>
Subject [jira] Commented: (MNG-2184) Possible problem with @aggregator and forked lifecycles
Date Fri, 08 Feb 2008 16:56:29 GMT


Brian Fox commented on MNG-2184:

The ounce:application goal is an aggregator that is intended to be bound to a pom. We need
to collect the information about all child projects. I think that where ever in the tree an
aggregator is defined, it should run once there. Meaning if it shows up in two children, well
then it runs for each of those (once for each of those trees)

The aggregation part isn't really what is needed if there is another way to get the fully
interpolated child projects....this is what is really needed.

> Possible problem with @aggregator and forked lifecycles
> -------------------------------------------------------
>                 Key: MNG-2184
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Design, Patterns & Best Practices, Plugins and Lifecycle
>    Affects Versions: 2.0.3
>         Environment: Revision 974 of Cargo (
>            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 (
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:
For more information on JIRA, see:


View raw message