Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.0.4
-
Fix Version/s: None
-
Component/s: Inheritance and Interpolation
-
Labels:None
-
Environment:Linux
-
Complexity:Intermediate
-
Number of attachments :
Description
My parent project defines the following:
<distributionManagement>
<snapshotRepository>
<id>Yo</id>
<name>Yo Repository</name>
<url>scp://yo/home/maven/www</url>
<uniqueVersion>false</uniqueVersion>
</snapshotRepository>
</distributionManagement>
When I run the following command in the child project:
mvn help:effective-pom
I get the following results:
...
<distributionManagement>
<snapshotRepository>
<id>Yo</id>
<name>Yo Repository</name>
<url>scp://yo/home/maven/www</url>
</snapshotRepository>
</distributionManagement>
...
It looks like inheritence is ignoring the <uniqueVersion> element.
This is also verified, when I run "mvn deploy" – the parent project installs a non-timestamped version in the remote repository, but the child project installs a timestamped version.
Issue Links
- is superceded by
-
MNG-3885
Modules of Maven projects are deployed with Timestamp during reactor build when uniqueVersion is set to false in parent profile
-
same issue as discussed here: http://jira.codehaus.org/browse/MNG-1094