[jira] Commented: (MNG-3885) Modules of Maven-Projects are deployed with Timestamp when uniqueVersion is set to false

["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