[ http://jira.codehaus.org/browse/MNG-250?page=comments#action_43522 ] 

John Casey commented on MNG-250:
--------------------------------

1. Plugins must declare @aggregator if they want to operate on the whole set of 
MavenProject instances at once without being applied repeatedly in standard 
reactor fashion.

2. LifecycleExecutor should preprocess the task list given from DefaultMaven 
(actually, from the CLI), and partition sets of tasks together, where 
continuous lists of non-aggregator tasks are grouped, and aggregator tasks are 
partitioned separately. Brett's example:

clean:clean install release:prepare site:site

are 3 partitions:

( clean:clean install ) ( release:prepare ) ( site:site )

To do this, we need to move MavenProject iteration out of DefaultMaven, and 
into the LE, right behind the aforementioned preprocessing/partitioning step. 
I'll use this as a jumping off point for implementation...

> make aggregation feasible
> -------------------------
>
>          Key: MNG-250
>          URL: http://jira.codehaus.org/browse/MNG-250
>      Project: Maven 2
>         Type: New Feature
>     Reporter: Brett Porter
>     Assignee: John Casey
>     Priority: Blocker
>      Fix For: 2.0-beta-1

>
>
> some plugins need to be able to aggregate, eg the assembly plugin could take 
> all the content based on its descriptor from the subprojects, and include 
> them under a base path. However, at the moment it runs across all of the 
> subprojects as well.
> Need to be able to have a goal turn off the execution of the reactor 
> (essentially it will be in aggregation mode), but have all the projects 
> available to it (possibly just collecting - see the other bug about reactor 
> execution modes).

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to