[
https://issues.apache.org/jira/browse/MDEPLOY-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965602#comment-17965602
]
Olivier Lamy commented on MDEPLOY-46:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#273|https://github.com/apache/maven-deploy-plugin/issues/273].
> "mvn -DaltDeploymentRepository=... deploy" of a SNAPSHOT doesn't replace
> date.buildnumber
> ------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-46
> URL: https://issues.apache.org/jira/browse/MDEPLOY-46
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Geoffrey De Smet
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
