You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Jackman (JIRA)" <ji...@codehaus.org> on 2007/03/22 15:42:34 UTC
[jira] Created: (MNG-2890) Allow for deploying to multiple
repositories
Allow for deploying to multiple repositories
--------------------------------------------
Key: MNG-2890
URL: http://jira.codehaus.org/browse/MNG-2890
Project: Maven 2
Issue Type: Improvement
Components: Deployment
Reporter: David Jackman
There is currently no way to list multiple repositories for deployment. When I've brought this question up before, people say to create mirrors of the repository, but that's not really the right solution in many cases. In my own case, I need to deploy to a Maven 1.x repository as well as the 2.x repository for the time being (while projects are moving from Maven 1 to Maven 2). This situation can't be solved by a repository mirror.
--
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
[jira] Closed: (MNG-2890) Allow for deploying to multiple
repositories
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-2890.
------------------------------
Resolution: Won't Fix
Deploying to multiple repositories is bad. It makes the resolving logic far more complex then necessary, having to look in multiple sources is not required. A project should deploy to one location and one location only.
> Allow for deploying to multiple repositories
> --------------------------------------------
>
> Key: MNG-2890
> URL: http://jira.codehaus.org/browse/MNG-2890
> Project: Maven 2
> Issue Type: Improvement
> Components: Deployment
> Reporter: David Jackman
>
> There is currently no way to list multiple repositories for deployment. When I've brought this question up before, people say to create mirrors of the repository, but that's not really the right solution in many cases. In my own case, I need to deploy to a Maven 1.x repository as well as the 2.x repository for the time being (while projects are moving from Maven 1 to Maven 2). This situation can't be solved by a repository mirror.
--
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