You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elad Tabak (JIRA)" <ji...@codehaus.org> on 2013/03/20 10:51:52 UTC

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

    [ https://jira.codehaus.org/browse/MNG-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322200#comment-322200 ] 

Elad Tabak commented on MNG-3885:
---------------------------------

Issue reproduced on maven 3.0.3.
Anyone aware of this?
                
> Modules of Maven projects are deployed with Timestamp during reactor build when uniqueVersion is set to false in parent profile
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3885
>                 URL: https://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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira