You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/06/16 03:02:12 UTC
[jira] Closed: (MNG-4709) Separate local repository for each remote
repository
[ http://jira.codehaus.org/browse/MNG-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-4709.
-----------------------------
Resolution: Duplicate
Assignee: Brett Porter
covered the use case of the subject in http://docs.codehaus.org/display/MAVEN/Local+repository+separation, waiting for after 3.0 and further discussion to consider working on it.
That said, I don't think having the same artifact in multiple different repositories is something that we want to encourage and an implementation would probably want a way to check for that.
> Separate local repository for each remote repository
> ----------------------------------------------------
>
> Key: MNG-4709
> URL: http://jira.codehaus.org/browse/MNG-4709
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Artifacts and Repositories
> Reporter: Paul Gier
> Assignee: Brett Porter
>
> It would be good if Maven used a separate local repository directory for each remote repository that was used. This would avoid the problem of two repositories using the same GAV for a different artifact. This would also allow the user to easily see where an artifact in the local repository was downloaded from.
> In addition the local repository used for "mvn install" could also be separated, so that it would not conflict with artifacts downloaded from remote repositories.
--
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