[jira] Closed: (MDEPLOY-46) "mvn -DaltDeploymentRepository=... deploy" of a SNAPSHOT doesn't replace date.buildnumber

["Stephen Connolly (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MDEPLOY-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Connolly closed MDEPLOY-46.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5

Marking as closed as the code contains the fix and this is also not an issue if using Maven 3 (as a side effect of Maven 3 dropping support for uniqueVersion=false)

> "mvn -DaltDeploymentRepository=... deploy" of a  SNAPSHOT doesn't replace date.buildnumber
> ------------------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-46
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-46
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>            Reporter: Geoffrey De Smet
>             Fix For: 2.5
>
>         Attachments: MDEPLOY-46.patch
>
>
> I 've checkouted a m2 project (spring-richclient) and deployed it to my local repo using the altDeploymentRepository parameter (from MDEPLOY-41).
> But the checkout is a SNAPSHOT version and the deployer should replace it with something like spring-richclient-core-0.3.0-20070101.160450-2.jar
> like the mvn deploy without altDeploymentRepository does,
> but it doesn't:
> [INFO] [deploy:deploy]
> altDeploymentRepository = ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev
> [INFO] Using alternate deployment repository ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev
> [INFO] Retrieving previous build number from ggg-dev
> Uploading: scp://mvn.ggg.be/maven/maven2/dev/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT.jar
> 50K uploaded

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira