[
http://jira.codehaus.org/browse/MDEPLOY-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey De Smet closed MDEPLOY-49.
-----------------------------------
Resolution: Duplicate
Fix Version/s: 2.5
Withdrawing issue, fixed in stage plugin, according to Wendy.
I 'll have to try out that stage plugin :) Currently we're using a custom hacky
script which also copies sources etc
> Gaol to copy artifact from one repo to another. deploy:deploy-from-other-repo
> -----------------------------------------------------------------------------
>
> Key: MDEPLOY-49
> URL: http://jira.codehaus.org/browse/MDEPLOY-49
> Project: Maven 2.x Deploy Plugin
> Issue Type: New Feature
> Reporter: Geoffrey De Smet
> Priority: Minor
> Fix For: 2.5
>
>
> The deploy plugin supports deploying from a local file with
> deploy:deploy-file,
> but it would be easier if it also supports fetching that file from another
> remote repo.
> Now we're using inhouse scripts to do this (which have problems).
> Archiva will support proxying the remote repo, but some orginazations don't
> want to automate adding artifacts to their release repo (only to their
> snapshot repo).
--
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
