[jira] Updated: (MNG-3885) Modules of Maven projects are deployed with Timestamp during reactor build when uniqueVersion is set to false in parent profile

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