Details
-
Bug
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
None
-
None
-
maven-3.1.0
Fedora 18 x86_64
Description
Consider the following scenario:
<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>
<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>
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
Attachments
Issue Links
- links to
- mentioned in
-
Page Loading...