[
https://issues.apache.org/jira/browse/MNG-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-7991:
-------------------------------
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...
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)
was:
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...
> refactor aggregator goal
> ------------------------
>
> Key: MNG-7991
> URL: https://issues.apache.org/jira/browse/MNG-7991
> Project: Maven
> Issue Type: Wish
> Components: Plugin API, Plugins and Lifecycle, Reactor and Workspace
> Affects Versions: 4.x / Backlog
> Reporter: Herve Boutemy
> Priority: Major
>
> 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...
> 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)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
