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/19 11:02:19 UTC

[jira] Created: (MNG-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent

[regression] Wrong order of plugin executions after merge with executions inherted from parent
----------------------------------------------------------------------------------------------

                 Key: MNG-3925
                 URL: http://jira.codehaus.org/browse/MNG-3925
             Project: Maven 2
          Issue Type: Bug
          Components: Plugins and Lifecycle
    Affects Versions: 3.0-alpha-1
            Reporter: Benjamin Bentmann


In Maven 2.x, plugin executions defined by the child are appended to the list of executions inherited from the parent. Maven 3.x breaks this behavior (currently also depending on the usage of {{<pluginManagement>}}.

-- 
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-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-3925:
-------------------------------

    Fix Version/s:     (was: 3.0-alpha-3)
                   3.0-alpha-4

> [regression] Wrong order of plugin executions after merge with executions inherted from parent
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-3925
>                 URL: http://jira.codehaus.org/browse/MNG-3925
>             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-4
>
>
> In Maven 2.x, plugin executions defined by the child are appended to the list of executions inherited from the parent. Maven 3.x breaks this behavior (currently also depending on the usage of {{<pluginManagement>}}.

-- 
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-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent

Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Isbell updated MNG-3925:
------------------------------

    Fix Version/s:     (was: 3.0-alpha-3)
                   3.0-alpha-2

Need to start bringing these into alpha-2 to get projects like nexus building.

> [regression] Wrong order of plugin executions after merge with executions inherted from parent
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-3925
>                 URL: http://jira.codehaus.org/browse/MNG-3925
>             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
>
>
> In Maven 2.x, plugin executions defined by the child are appended to the list of executions inherited from the parent. Maven 3.x breaks this behavior (currently also depending on the usage of {{<pluginManagement>}}.

-- 
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-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent

Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Isbell updated MNG-3925:
------------------------------

    Fix Version/s:     (was: 3.0-alpha-2)
                   3.0-alpha-3

> [regression] Wrong order of plugin executions after merge with executions inherted from parent
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-3925
>                 URL: http://jira.codehaus.org/browse/MNG-3925
>             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-3
>
>
> In Maven 2.x, plugin executions defined by the child are appended to the list of executions inherited from the parent. Maven 3.x breaks this behavior (currently also depending on the usage of {{<pluginManagement>}}.

-- 
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-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-3925:
-------------------------------

    Fix Version/s:     (was: 3.0-alpha-4)
                   3.0-alpha-3

> [regression] Wrong order of plugin executions after merge with executions inherted from parent
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-3925
>                 URL: http://jira.codehaus.org/browse/MNG-3925
>             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-3
>
>
> In Maven 2.x, plugin executions defined by the child are appended to the list of executions inherited from the parent. Maven 3.x breaks this behavior (currently also depending on the usage of {{<pluginManagement>}}.

-- 
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-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3925:
------------------------------

    Fix Version/s: 3.0-alpha-3

> [regression] Wrong order of plugin executions after merge with executions inherted from parent
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-3925
>                 URL: http://jira.codehaus.org/browse/MNG-3925
>             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
>
>
> In Maven 2.x, plugin executions defined by the child are appended to the list of executions inherited from the parent. Maven 3.x breaks this behavior (currently also depending on the usage of {{<pluginManagement>}}.

-- 
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-3925) [regression] Wrong order of plugin executions after merge with executions inherted from parent

Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Isbell closed MNG-3925.
-----------------------------

    Resolution: Fixed

> [regression] Wrong order of plugin executions after merge with executions inherted from parent
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-3925
>                 URL: http://jira.codehaus.org/browse/MNG-3925
>             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-3
>
>
> In Maven 2.x, plugin executions defined by the child are appended to the list of executions inherited from the parent. Maven 3.x breaks this behavior (currently also depending on the usage of {{<pluginManagement>}}.

-- 
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