[
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
