Refactor lifecycle executor to allow viewing/modification of a declarative
build 'plan'
---------------------------------------------------------------------------------------
Key: MNG-2863
URL: http://jira.codehaus.org/browse/MNG-2863
Project: Maven 2
Issue Type: New Feature
Components: Plugins and Lifecycle
Affects Versions: 2.0.5
Reporter: John Casey
Fix For: 2.1.x
Currently, Maven basically discovers the next step in the build once the last
one is executed, according to profile injection, POM inheritance, lifecycle
mappings, and the default mojos bound to a give lifecycle. The fact that all of
this happens "magically" (completely behind the scenes) makes it quite
difficult to understand how the build will execute ahead of time in some cases.
If a given mojo specifies an @execute annotation, then this can further
confound users trying to understand the build process.
As preparation for adding fine-grained mojo ordering within a phase, as well as
mojo suppression and replacement, we need the ability to see ahead of a build's
execution exactly what steps it will traverse. This should act much like the
effective-pom or effective-settings as a diagnosis tool, and help users target
certain behaviors they want to modify through their POMs.
--
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
