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 2010/11/24 00:11:03 UTC

[jira] Created: (MNG-4913) [regression] User properties override equally named POM properties of transitive dependencies

[regression] User properties override equally named POM properties of transitive dependencies
---------------------------------------------------------------------------------------------

                 Key: MNG-4913
                 URL: http://jira.codehaus.org/browse/MNG-4913
             Project: Maven 2 & 3
          Issue Type: Bug
          Components: Artifacts and Repositories
    Affects Versions: 3.0
            Reporter: Benjamin Bentmann


While trying to run the core ITs using {{-DmavenVersion=3.0.1}} the build ended up with a resolution failures for a bunch of non-existing artifacts like {{maven-reporting-api:3.0.1}}. The problematic artifact versions were coming from a wrong dependency tree like this:
{noformat}
DEBUG] org.apache.maven.plugins:maven-resources-plugin:jar:2.3:
DEBUG]    org.apache.maven:maven-plugin-api:jar:2.0.6:compile
DEBUG]    org.apache.maven:maven-project:jar:2.0.6:compile
DEBUG]       org.apache.maven:maven-settings:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-profile:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-model:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-artifact-manager:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-plugin-registry:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-artifact:jar:3.0.1:compile
{noformat}
Note that the dependencies of {{maven-project:2.0.6}} use the wrong version.

The problem is due to {{maven:pom:2.0.6}} using the POM property {{mavenVersion}} which erroneously gets overridden by my user property.

During dependency resolution, user properties must be treated like system properties and must not override POM properties.

-- 
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-4913) [regression] User properties override equally named POM properties of transitive dependencies

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

Benjamin Bentmann closed MNG-4913.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.2
         Assignee: Benjamin Bentmann

Fixed in [r1038391|http://svn.apache.org/viewvc?view=revision&revision=1038391].

> [regression] User properties override equally named POM properties of transitive dependencies
> ---------------------------------------------------------------------------------------------
>
>                 Key: MNG-4913
>                 URL: http://jira.codehaus.org/browse/MNG-4913
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.0
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0.2
>
>
> While trying to run the core ITs using {{-DmavenVersion=3.0.1}} the build ended up with a resolution failures for a bunch of non-existing artifacts like {{maven-reporting-api:3.0.1}}. The problematic artifact versions were coming from a wrong dependency tree like this:
> {noformat}
> DEBUG] org.apache.maven.plugins:maven-resources-plugin:jar:2.3:
> DEBUG]    org.apache.maven:maven-plugin-api:jar:2.0.6:compile
> DEBUG]    org.apache.maven:maven-project:jar:2.0.6:compile
> DEBUG]       org.apache.maven:maven-settings:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-profile:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-model:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-artifact-manager:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-plugin-registry:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-artifact:jar:3.0.1:compile
> {noformat}
> Note that the dependencies of {{maven-project:2.0.6}} use the wrong version.
> The problem is due to {{maven:pom:2.0.6}} using the POM property {{mavenVersion}} which erroneously gets overridden by my user property.
> During dependency resolution, user properties must be treated like system properties and must not override POM properties.

-- 
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] Commented: (MNG-4913) [regression] User properties override equally named POM properties of transitive dependencies

Posted by "Ralph Goers (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244220#action_244220 ] 

Ralph Goers commented on MNG-4913:
----------------------------------

Actually, this strikes me as being a duplicate of MNG-2971. Once an artifact has been installed these variables should have been replaced with the variables used during the release.

> [regression] User properties override equally named POM properties of transitive dependencies
> ---------------------------------------------------------------------------------------------
>
>                 Key: MNG-4913
>                 URL: http://jira.codehaus.org/browse/MNG-4913
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.0
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0.2
>
>
> While trying to run the core ITs using {{-DmavenVersion=3.0.1}} the build ended up with a resolution failures for a bunch of non-existing artifacts like {{maven-reporting-api:3.0.1}}. The problematic artifact versions were coming from a wrong dependency tree like this:
> {noformat}
> DEBUG] org.apache.maven.plugins:maven-resources-plugin:jar:2.3:
> DEBUG]    org.apache.maven:maven-plugin-api:jar:2.0.6:compile
> DEBUG]    org.apache.maven:maven-project:jar:2.0.6:compile
> DEBUG]       org.apache.maven:maven-settings:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-profile:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-model:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-artifact-manager:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-plugin-registry:jar:3.0.1:compile
> DEBUG]       org.apache.maven:maven-artifact:jar:3.0.1:compile
> {noformat}
> Note that the dependencies of {{maven-project:2.0.6}} use the wrong version.
> The problem is due to {{maven:pom:2.0.6}} using the POM property {{mavenVersion}} which erroneously gets overridden by my user property.
> During dependency resolution, user properties must be treated like system properties and must not override POM properties.

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