You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/05/01 04:28:47 UTC

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

     [ http://jira.codehaus.org/browse/MNG-250?page=comments#action_38369 ]
     
Brett Porter commented on MNG-250:
----------------------------------

in this case, a coupld of other features need to be implemented:
- the code from DefaultMaven that does the project aggregation should be moved into the project builder as an optional function
- dependency resolution that is triggered by a goal on the main project would also need to resolve dependencies of the collected projects on an aggregation enabled project


> make aggregation feasible
> -------------------------
>
>          Key: MNG-250
>          URL: http://jira.codehaus.org/browse/MNG-250
>      Project: m2
>         Type: New Feature
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Minor
>      Fix For: 2.0-alpha-2

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