You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bob Fields (JIRA)" <ji...@codehaus.org> on 2010/02/04 21:44:55 UTC
[jira] Commented: (MNG-3885) Modules of Maven projects are deployed
with Timestamp during reactor build when uniqueVersion is set to false in
parent profile
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209195#action_209195 ]
Bob Fields commented on MNG-3885:
---------------------------------
We are seeing this issue in maven 2.2.1. A parent pom.xml with many submodules, was changed from uniqueVersion=true to uniqueVersion=false. No other repository configuration exists in any submodules. Child maven-metadata.xml files already existed with <versioning> info. The parent maven-metadata.xml file does not have a <versioning> section, but the child maven-metadata.xml files still have the old <versioning> info, causing a mismatch in dependencies.
Parent maven-metadata: http://oss.sonatype.org/content/groups/public/org/andromda/andromda/3.4-SNAPSHOT/maven-metadata.xml
Child maven-metadata: http://oss.sonatype.org/content/groups/public/org/andromda/andromda-core/3.4-SNAPSHOT/maven-metadata.xml
> Modules of Maven projects are deployed with Timestamp during reactor build when uniqueVersion is set to false in parent profile
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 2.0.8
> Environment: Red Hat Linux, Maven 2.0.8, Java 1.6, Cruisecontrol
> Reporter: Matthias Wegerhoff
> Assignee: Benjamin Bentmann
> Fix For: 2.0.11, 2.1.0-M1, 3.0-alpha-3
>
> Attachments: minimizedPOM.xml, minimizedPOM.xml, minimizedSETTINGS.xml, MNG-3885.zip
>
>
> When deploying artifacts into local repository with cruisecontrol by using the following command:
> mvn -U -P mvn-profile ... -DuniqueVersion=false deploy
> The parent is always beeing deployed correctly, without timestamp as <MODULE_VERSION>-SNAPSHOT. But all Modules are beeing deployed with Timestamp.
--
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