Details
-
Wish
-
Status: Open
-
Major
-
Resolution: Unresolved
-
4.x / Backlog
-
None
-
None
Description
aggregation was added in early Maven 2 stages with MNG-250, not really documented AFAIK
there are multiple shortcomings found over time:
- discrepancy between CLI and lifecycle use: CLI skips execution in sub-modules, but not lifecycle
- forked lifecycle execution vs second execution in modules
- sometimes, instead of executing aggregate goal before building modules, it would be useful to execute aggregate after building modules (to aggregate some results built in each module)
notice that this looks also like the need for "execute at end" as found in install/deploy
we probably need to better document what aggregate currently does and define what should be the target: perhaps refactoring will require new mechanisms that we won't call aggregator, like MNG-5665...
edge case: aggregating reports for maven-site-plugin (launched by maven-reporting-exec, hence quite independent from associated reporting goals even if we expect some consistency between site reports and reporting goals)
Attachments
Issue Links
- contains
-
MNG-2184 Possible problem with @aggregator and forked lifecycles
- Open
- incorporates
-
MNG-6336 Aggregator Mojo should be executed only once even when part of the lifecycle
- Open
- is caused by
-
MNG-250 make aggregation feasible
- Closed
- is related to
-
MNG-7900 wrapper lifecycle in multi module project should be executed only in root module
- Open
- relates to
-
MNG-5665 Advanced Lifecycle Handling
- Open
-
MNG-7163 Aggregating Mojo re-executes goals for child modules that are already executed
- Open
-
MNG-7672 Aggregate goals executed in a submodule forks the whole reactor
- Closed
-
MNG-2180 Allow aggregation mojos to access plugin configurations
- Closed
-
MNG-4504 Disallowing all aggregator bindings to any lifecycle is too broad
- Closed