You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matthias Wegerhoff (JIRA)" <ji...@codehaus.org> on 2008/12/02 16:19:19 UTC
[jira] Created: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
----------------------------------------------------------------------------------------
Key: MNG-3885
URL: http://jira.codehaus.org/browse/MNG-3885
Project: Maven 2
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
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
[jira] Commented: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Matthias Wegerhoff (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156446#action_156446 ]
Matthias Wegerhoff commented on MNG-3885:
-----------------------------------------
I recognized that this only happens when deploying snapshots with a profile defined in settings.xml. When defining Repositories in a profile in settings xml and deploying the artifact by using this profile with
mvn -U -P mvn-profile ... -DuniqueVersion=false deploy
all modules are beeing deployed with timestamps.
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
>
> 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
[jira] Commented: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Matthias Wegerhoff (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158518#action_158518 ]
Matthias Wegerhoff commented on MNG-3885:
-----------------------------------------
No, they lust define their parent:
<parent>
<artifactId>example</artifactId>
<groupId>de.myCompany</groupId>
<version>trunk-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
Do I have to add an seperate profile/distributionManagement section in every child-pom?
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
> Attachments: minimizedPOM.xml, minimizedPOM.xml, minimizedSETTINGS.xml
>
>
> 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
[jira] Commented: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158491#action_158491 ]
Brett Porter commented on MNG-3885:
-----------------------------------
given these settings, I expect -DuniqueVersion=true|false to have no effect.
So since the POM defines it with <uniqueVersion>false</uniqueVersion> that should be honoured. Is that what is happening?
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
> Attachments: minimizedPOM.xml, minimizedPOM.xml, minimizedSETTINGS.xml
>
>
> 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
[jira] Updated: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3885:
------------------------------
Attachment: MNG-3885.zip
I can't reproduce the problem. See attached test case
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
> 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
[jira] Updated: (MNG-3885) Modules of Maven projects are deployed
with Timestamp during reactor build when uniqueVersion is set to false in
parent profile
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-3885:
-----------------------------------
Summary: Modules of Maven projects are deployed with Timestamp during reactor build when uniqueVersion is set to false in parent profile (was: Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false)
> 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
> 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
> 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
[jira] Commented: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158510#action_158510 ]
Brett Porter commented on MNG-3885:
-----------------------------------
do your child modules declare a repository as well?
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
> Attachments: minimizedPOM.xml, minimizedPOM.xml, minimizedSETTINGS.xml
>
>
> 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
[jira] Commented: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Matthias Wegerhoff (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158501#action_158501 ]
Matthias Wegerhoff commented on MNG-3885:
-----------------------------------------
Defining <uniqueVersion>false</uniqueVersion> in the projects pom.xml takes only effect on the parent but not on child-modules. No matter if i´m calling the deploy-goal with or without the parameter -DuniqueVerison=false
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
> Attachments: minimizedPOM.xml, minimizedPOM.xml, minimizedSETTINGS.xml
>
>
> 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
[jira] Commented: (MNG-3885) Modules of Maven projects are deployed
with Timestamp during reactor build when uniqueVersion is set to false in
parent profile
Posted by "Bob Fields (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-3885) Modules of Maven projects are deployed
with Timestamp during reactor build when uniqueVersion is set to false in
parent profile
Posted by "Bob Fields (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209201#action_209201 ]
Bob Fields commented on MNG-3885:
---------------------------------
Sorry, we had to delete and re-create the referenced artifacts because everybody was broken, so they are correct currently. Deleting the old maven-metadata.xml files caused new ones to be created correctly, without the versioning info, however the deploy plugin really should update the metadata correctly without having to delete.
> 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
[jira] Updated: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Matthias Wegerhoff (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Wegerhoff updated MNG-3885:
------------------------------------
Attachment: minimizedPOM.xml
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
> Attachments: minimizedPOM.xml, minimizedPOM.xml, minimizedSETTINGS.xml
>
>
> 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
[jira] Updated: (MNG-3885) Modules of Maven projects are deployed
with Timestamp during reactor build when uniqueVersion is set to false in
parent profile
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-3885:
-----------------------------------
Fix Version/s: 3.0-alpha-3
> 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
> 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
[jira] Updated: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Matthias Wegerhoff (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Wegerhoff updated MNG-3885:
------------------------------------
Attachment: minimizedSETTINGS.xml
minimizedPOM.xml
Thanks for your response, i attached a minimized pom.xml as well as a minimized settings.xml that is used by out build-server.
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
> Attachments: minimizedPOM.xml, minimizedSETTINGS.xml
>
>
> 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
[jira] Closed: (MNG-3885) Modules of Maven projects are deployed
with Timestamp during reactor build when uniqueVersion is set to false in
parent profile
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-3885.
----------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1.0-M1
2.0.11
Fixed in [r737402|http://svn.eu.apache.org/viewvc?view=rev&revision=737402]. Already works in Maven 2.1.x as of [r689163|http://svn.eu.apache.org/viewvc?view=rev&revision=689163].
> 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
> 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
>
> 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
[jira] Commented: (MNG-3885) Modules of Maven-Projects are deployed
with Timestamp when uniqueVersion is set to false
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158438#action_158438 ]
Brett Porter commented on MNG-3885:
-----------------------------------
are you defining uniqueVersion in your POM somehow? It is not an option to Maven or the deploy plugin, so it would need to be substituted into the distributionManagement element of your POM.
Could you provide a small number of POMs that illustrates the problem?
> Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3885
> URL: http://jira.codehaus.org/browse/MNG-3885
> Project: Maven 2
> 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
>
> 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