[
https://issues.apache.org/jira/browse/MDEPLOY-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965596#comment-17965596
]
Olivier Lamy commented on MDEPLOY-41:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#257|https://github.com/apache/maven-deploy-plugin/issues/257].
> Deploying to alternate repo specified by -DrepositoryId=
> --------------------------------------------------------
>
> Key: MDEPLOY-41
> URL: https://issues.apache.org/jira/browse/MDEPLOY-41
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Wish
> Reporter: Brian Topping
> Assignee: Jason van Zyl
> Priority: Major
> Fix For: 2.3
>
>
> It's useful to be able to build an artifact (such as a snapshot of a plugin)
> and deploy it to a local repository (such as on a corporate intranet).
> A good way to do this seems to be putting the corporate repo into
> settings.xml and using -DrepositoryId=xxx on the command line, but this
> doesn't work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
