You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/12/02 18:53:19 UTC
[jira] Created: (MNG-3887) Order of plugin executions within same
phase does not match POM order when plugin management is used
Order of plugin executions within same phase does not match POM order when plugin management is used
----------------------------------------------------------------------------------------------------
Key: MNG-3887
URL: http://jira.codehaus.org/browse/MNG-3887
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
For a POM snippet like
{code:xml}
<executions>
<execution>
<id>test-1</id>
<phase>validate</phase>
<goals>
<goal>one</goal>
</goals>
</execution>
<execution>
<id>test-2</id>
<phase>validate</phase>
<goals>
<goal>two</goal>
</goals>
</execution>
</executions>
{code}
the effective goal execution order is either [one, two] or [two, one] depending on the usage of {{<pluginManagement>}} for the plugin in question.
--
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
[jira] Updated: (MNG-3887) [regression] Order of plugin executions
within same phase does not match POM order when plugin management is used
Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shane Isbell updated MNG-3887:
------------------------------
Fix Version/s: (was: 3.0-alpha-3)
3.0-alpha-2
> [regression] Order of plugin executions within same phase does not match POM order when plugin management is used
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3887
> URL: http://jira.codehaus.org/browse/MNG-3887
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-alpha-1
> Reporter: Benjamin Bentmann
> Assignee: Shane Isbell
> Fix For: 3.0-alpha-2
>
>
> For a POM snippet like
> {code:xml}
> <executions>
> <execution>
> <id>test-1</id>
> <phase>validate</phase>
> <goals>
> <goal>one</goal>
> </goals>
> </execution>
> <execution>
> <id>test-2</id>
> <phase>validate</phase>
> <goals>
> <goal>two</goal>
> </goals>
> </execution>
> </executions>
> {code}
> the effective goal execution order is either [one, two] or [two, one] depending on the usage of {{<pluginManagement>}} for the plugin in question.
--
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
[jira] Closed: (MNG-3887) [regression] Order of plugin executions
within same phase does not match POM order when plugin management is used
Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shane Isbell closed MNG-3887.
-----------------------------
Resolution: Fixed
> [regression] Order of plugin executions within same phase does not match POM order when plugin management is used
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3887
> URL: http://jira.codehaus.org/browse/MNG-3887
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-alpha-1
> Reporter: Benjamin Bentmann
> Assignee: Shane Isbell
> Fix For: 3.0-alpha-2
>
>
> For a POM snippet like
> {code:xml}
> <executions>
> <execution>
> <id>test-1</id>
> <phase>validate</phase>
> <goals>
> <goal>one</goal>
> </goals>
> </execution>
> <execution>
> <id>test-2</id>
> <phase>validate</phase>
> <goals>
> <goal>two</goal>
> </goals>
> </execution>
> </executions>
> {code}
> the effective goal execution order is either [one, two] or [two, one] depending on the usage of {{<pluginManagement>}} for the plugin in question.
--
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
[jira] Updated: (MNG-3887) [regression] Order of plugin executions
within same phase does not match POM order when plugin management is used
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-3887:
-----------------------------------
Summary: [regression] Order of plugin executions within same phase does not match POM order when plugin management is used (was: Order of plugin executions within same phase does not match POM order when plugin management is used)
> [regression] Order of plugin executions within same phase does not match POM order when plugin management is used
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3887
> URL: http://jira.codehaus.org/browse/MNG-3887
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-alpha-1
> Reporter: Benjamin Bentmann
>
> For a POM snippet like
> {code:xml}
> <executions>
> <execution>
> <id>test-1</id>
> <phase>validate</phase>
> <goals>
> <goal>one</goal>
> </goals>
> </execution>
> <execution>
> <id>test-2</id>
> <phase>validate</phase>
> <goals>
> <goal>two</goal>
> </goals>
> </execution>
> </executions>
> {code}
> the effective goal execution order is either [one, two] or [two, one] depending on the usage of {{<pluginManagement>}} for the plugin in question.
--
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
[jira] Updated: (MNG-3887) [regression] Order of plugin executions
within same phase does not match POM order when plugin management is used
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3887:
------------------------------
Fix Version/s: 3.0-alpha-3
> [regression] Order of plugin executions within same phase does not match POM order when plugin management is used
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3887
> URL: http://jira.codehaus.org/browse/MNG-3887
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-alpha-1
> Reporter: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> For a POM snippet like
> {code:xml}
> <executions>
> <execution>
> <id>test-1</id>
> <phase>validate</phase>
> <goals>
> <goal>one</goal>
> </goals>
> </execution>
> <execution>
> <id>test-2</id>
> <phase>validate</phase>
> <goals>
> <goal>two</goal>
> </goals>
> </execution>
> </executions>
> {code}
> the effective goal execution order is either [one, two] or [two, one] depending on the usage of {{<pluginManagement>}} for the plugin in question.
--
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