Matous Jobanek created MNG-5527:
-----------------------------------

             Summary: Relocation does not work for imported BOMs
                 Key: MNG-5527
                 URL: https://jira.codehaus.org/browse/MNG-5527
             Project: Maven 2 & 3
          Issue Type: Bug
          Components: Dependencies
         Environment: maven-3.1.0
Fedora 18 x86_64
            Reporter: Matous Jobanek


Consider the following scenario:

{code:xml}
<project>
    <modelVersion>4.0.0</modelVersion>
    <groupId>old.groupId.bom</groupId>
    <artifactId>my-artifactId-bom</artifactId>
    <version>1.0</version>
    <packaging>pom</packaging>

    <distributionManagement>
        <relocation>
            <groupId>new.groupId.bom</groupId>
            <artifactId>my-artifactId-bom</artifactId>
            <version>2.0</version>
        </relocation>
    </distributionManagement>
</project>
{code}

{code:xml}
<project>
    <modelVersion>4.0.0</modelVersion>

    <groupId>my.project.groupId</groupId>
    <artifactId>my-project</artifactId>
    <version>1.0</version>
    <packaging>war</packaging>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>old.groupId.bom</groupId>
                <artifactId>my-artifactId-bom</artifactId>
                <version>1.0</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

    ...

</project>
{code}


The expected result according to [1]:
During building the "my-project" it should print the WARNING with the 
information about the relocation and it should be automatically redirected from 
old.groupId.bom:my-artifactId-bom:1.0 to new.groupId.bom:my-artifactId-bom:2.0 
and use dependencies from the new pom.


Actual results:
There is no WARNING and no redirection to the new pom and maven is trying to 
obtain dependencies from the old pom (old.groupId.bom:my-artifactId-bom:1.0).  
Nevertheless, when the pom is declared as a "normal dependency" (not in the 
"dependencyManagement" part) it works without any problem - it prints the 
WARNING and redirects to the new pom, but this is not the case we are using.

[1] http://maven.apache.org/guides/mini/guide-relocation.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to