Christoph Läubrich created MNG-8557:
---------------------------------------
Summary: Support for binding a mojo to an "after all" phase
Key: MNG-8557
URL: https://issues.apache.org/jira/browse/MNG-8557
Project: Maven
Issue Type: Improvement
Reporter: Christoph Läubrich
In some situations (e.g. javadoc aggregation, install-at-end, deploy-at-end) it
would be helpful to allow a mojo to run "after all projects have completed
phase X" that is similar to what currently is provided by an "aggregation" mojo
but at a finer grained level.
Lets assume I have an execution bound to the theoretical syntax
{code}package:all{code} I would expect the following:
# my mojo is not executed at the package phase for each individual project
# my mojo is executed after all projects in the reactor have run the package
phase
# beside that it works like a usual execution so my mojo is executed for each
project individually, maybe in parallel
As Maven 3 can currently not interleave build phases, this is likely only
possible to implement with Maven 4 but would prevent several hacks in
maven-core-plugins but also in extensions (e.g. Tycho).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
