[jira] Closed: (MNG-250) make aggregation feasible

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

     [ http://jira.codehaus.org/browse/MNG-250?page=all ]
     
John Casey closed MNG-250:
--------------------------

    Resolution: Fixed

NOTE: currently using straight reactored builds ('-r' builds) with aggregator plugins CAN result in weirdness, since there is no clean hierarchy of projects, and the first one read into the system will be the one from which plugin configuration is read during task segmentation (not sure that this matters at all, actually, but just mentioning it...).

I'll let it get logged as a bug if there are specific cases where this is a problem.

> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org