Details
-
New Feature
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
None
Description
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).
Attachments
Issue Links
- causes
-
MNG-7991 refactor "aggregator" goal feature
- Open
- is depended upon by
-
MNG-662 Refactor release plugin to handle reactored build and release-pom.xml-SCM interactions.
- Closed
-
MNG-148 Write an ear mojo
- Closed
- is related to
-
MNG-7163 Aggregating Mojo re-executes goals for child modules that are already executed
- Open
-
MNG-3716 Aggregators that fork lifecycles don't have execution projects setup for all projects in the reactor.
- Closed
-
MNG-1073 aggregating goal does not fork a lifecycle
- Closed
-
MNG-2028 Attached mojos with the @aggregator tag can yield bad results in a multi-module project
- Closed
-
MNG-4314 [regression] Direct invocation of aggregator plugin causes plugin to run on each project
- Closed
-
MNG-4320 [regression] Aggregators invoked from CLI no longer resolve dependencies for all reactor projects
- Closed
-
MNG-4325 [regression] Lifecycle overlay configuration of aggregator mojos is not properly processed when forking reactor
- Closed
-
MNG-5565 Aggregator style plugin with requiresDependencyResolution retrieving artefacts from remote instead of reactor
- Closed
-
MNG-7672 Aggregate goals executed in a submodule forks the whole reactor
- Closed
-
MNG-2180 Allow aggregation mojos to access plugin configurations
- Closed
-
MNG-7476 Display a warning when an aggregator mojo is locking other mojo executions
- Closed