Sander Verhagen created MNG-5521:
------------------------------------
Summary: Merge plugin lifecycle execution with actual build
Key: MNG-5521
URL: https://jira.codehaus.org/browse/MNG-5521
Project: Maven 2 & 3
Issue Type: Improvement
Affects Versions: 3.0.5
Reporter: Sander Verhagen
Priority: Minor
Plugins annotated with @Execute (org.apache.maven.plugins.annotations.Execute)
will run a build for the specified lifecycle phase, regardless of anything
previously executed. This is relevant when such plugin is defined within the
lifecycle, but may even be relevant if the plugin is defined on the
command-line following a lifecycle build (e.g.: mvn process-classes
tomcat7:run).
This has two negative consequences:
1. Even if the build was already advanced to or past the specified lifecycle
phase, a build for the specified lifecycle phase will be spun off which redoes
the build for no good reason
2. While the build for the specified lifecycle phase is performed, it may undo
any previous more advanced build. E.g. if the specified lifecycle phase is
"compile", but the plugin is executed in the "test" phase, any results of the
"process-classes" phase may be undone
An example of the problems caused with this can be found here:
http://stackoverflow.com/questions/18965550/influence-the-lifecycle-execution-that-a-maven-plugin-executes-tomcat7run#comment28012573_18965550
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
