You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/08/14 17:30:26 UTC

[jira] Created: (MNG-3710) ModelUtils.cloneModel() and .cloneBuild() pollute existing Plugin instances with merged information

ModelUtils.cloneModel() and .cloneBuild() pollute existing Plugin instances with merged information
---------------------------------------------------------------------------------------------------

                 Key: MNG-3710
                 URL: http://jira.codehaus.org/browse/MNG-3710
             Project: Maven 2
          Issue Type: Bug
          Components: Inheritance and Interpolation
    Affects Versions: 2.0.10
            Reporter: John Casey
            Priority: Blocker
             Fix For: 2.0.10


Plugin information that gets merged with handleAsInheritance == false results in pollution of the original Plugin instance by that from the new one. This means pluginManagement specified in a child POM can affect the Plugin instance that's actually declared in the parent POM.

-- 
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-3710) ModelUtils.cloneModel() and .cloneBuild() pollute existing Plugin instances with merged information

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

John Casey closed MNG-3710.
---------------------------

    Resolution: Fixed

> ModelUtils.cloneModel() and .cloneBuild() pollute existing Plugin instances with merged information
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3710
>                 URL: http://jira.codehaus.org/browse/MNG-3710
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>            Priority: Blocker
>             Fix For: 2.0.10
>
>
> Plugin information that gets merged with handleAsInheritance == false results in pollution of the original Plugin instance by that from the new one. This means pluginManagement specified in a child POM can affect the Plugin instance that's actually declared in the parent POM.

-- 
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] Work started: (MNG-3710) ModelUtils.cloneModel() and .cloneBuild() pollute existing Plugin instances with merged information

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

Work on MNG-3710 started by John Casey.

> ModelUtils.cloneModel() and .cloneBuild() pollute existing Plugin instances with merged information
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3710
>                 URL: http://jira.codehaus.org/browse/MNG-3710
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>            Priority: Blocker
>             Fix For: 2.0.10
>
>
> Plugin information that gets merged with handleAsInheritance == false results in pollution of the original Plugin instance by that from the new one. This means pluginManagement specified in a child POM can affect the Plugin instance that's actually declared in the parent POM.

-- 
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-3710) ModelUtils.cloneModel() and .cloneBuild() pollute existing Plugin instances with merged information

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

John Casey updated MNG-3710:
----------------------------

         Assignee: John Casey
    Fix Version/s: 2.0.10

> ModelUtils.cloneModel() and .cloneBuild() pollute existing Plugin instances with merged information
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3710
>                 URL: http://jira.codehaus.org/browse/MNG-3710
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0.10
>            Reporter: John Casey
>            Assignee: John Casey
>            Priority: Blocker
>             Fix For: 2.0.10
>
>
> Plugin information that gets merged with handleAsInheritance == false results in pollution of the original Plugin instance by that from the new one. This means pluginManagement specified in a child POM can affect the Plugin instance that's actually declared in the parent POM.

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