Support configuring plugins that always execute
-----------------------------------------------
Key: MNG-2073
URL: http://jira.codehaus.org/browse/MNG-2073
Project: Maven 2
Type: New Feature
Components: Plugins and Lifecycle
Reporter: John Didion
Currently, there is no way to set up a plugin to run every time I invoke maven
on my project, regardless of whether I'm executing a stand-alone goal or a
lifecycle phase. For example, I have a plugin that munges some project
information and sets project properties based on the results. I want to use
these properties elsewhere in my project file. It would be nice if I could set
up this plugin to always be the first thing that executes when I invoke maven
on my project. I'm thinking something like the following:
{noformat}
<project>
<globalPlugins>
<plugin>
...
</plugin>
</globalPlugins>
</project>
{noformat}
These plugins obviously wouldn't support the phase and goal tags within
executions.
Another way to accomplish this would be to recognize a special phase called
"global" (or something similar) that would indicate a plugin that always runs
first (i.e. before starting the lifecycle or executing stand-alone goals). For
example:
{noformat}
<project>
<plugins>
<plugin>
<groupId>foo</groupId>
<artifactId>bar</artifactId>
<executions>
<execution>
<phase>global</phase>
<goals>
<goal>baz</goal>
</goals>
<configuration>
...
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</project>
{noformat}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
