You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Geoffrey De Smet (JIRA)" <ji...@codehaus.org> on 2007/01/04 17:06:09 UTC
[jira] Commented: (MDEPLOY-41) Deploying to alternate repo
specified by -DrepositoryId=
[ http://jira.codehaus.org/browse/MDEPLOY-41?page=comments#action_84023 ]
Geoffrey De Smet commented on MDEPLOY-41:
-----------------------------------------
Nice, but for SNAPSHOT it doesn't quite work a 100% yet (the remote repo might even be considered slightly corrupted by it), see MDEPLOY-46
> Deploying to alternate repo specified by -DrepositoryId=
> --------------------------------------------------------
>
> Key: MDEPLOY-41
> URL: http://jira.codehaus.org/browse/MDEPLOY-41
> Project: Maven 2.x Deploy Plugin
> Issue Type: Wish
> Reporter: Brian Topping
> Assigned To: Jason van Zyl
> 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 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