This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Local Repository Separation

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


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

Proposed Solution

To solve this problem, Maven should use a separate local repository for each remote repository. Each local repository would function as a cache for the associated remote repository. The name of each local repository cache follows the format <repositoryId>-<url-hash>. In the event that the same repository ID is used to represent two different remote URLs, two separate repository caches would be created. If two repository IDs point to the same URL, the hash value can be used to identify that they are the same, and possibly store metadata that allows Maven to recognize the two as being the same.


No Format
+- repositories
|  +- central-<hash>
|  +- repoA-<hash>
|  \- repoB-<hash>
\- workspace

Related Jira issues http

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