Page History

...

If repo A is specified first in the build config, then the jar and pom from repo A will be downloaded to the local repository. If another build is then run which requires org:myproj:1.0 from repo B, Maven will use the incorrect jar and POM from repo A, since it is already available in the local repo. This is known as a GAV conflict because the two repositories have conflicting data and cannot be safely used together.

Related Discussion: http://docs.codehaus.org/display/MAVEN/Local+repository+separation^{Image Removed}

Proposed Solution

...

.m2
+- repositories
|  +- central-<hash>
|  +- repoA-<hash>
|  \- repoB-<hash>
\- workspace

Related Jira issues http://jira.codehaus.org/browse/MNG-3655^{Image Removed}http://jira.codehaus.org/browse/MNG-4709^{Image Removed}

Repositories vs. Plugin Repositories

This proposal is also related to separation of repositories for project dependencies is the use of plugin repositories as discussed in http://jira.codehaus.org/browse/MNG-4302^{Image Removed}