-
Task
-
Resolution: Unresolved
-
Major
-
None
-
8.1.0.GA
-
None
-
False
-
-
False
-
-
-
-
example-settings.xml is bundled within maven-repository.zip deliverable and it looks like this:
....
<repositories>
<repository>
<id>jboss-eap-repository</id>
<url>file:///path/to/repo/jboss-eap-8.1.0.GA-maven-repository/maven-repository</url>
....
<pluginRepositories>
<pluginRepository>
<id>jboss-eap-plugin-repository</id>
<url>file:///path/to/repo/jboss-eap-8.1.0.GA-maven-repository/maven-repository</url>
....
<id>jboss-community-repository</id>
<repositories>
<repository>
<id>jboss-community-repository</id>
<url>https://repository.jboss.org/nexus/content/groups/public/</url>
....
<pluginRepositories>
<pluginRepository>
<id>jboss-community-plugin-repository</id>
<url>https://repository.jboss.org/nexus/content/groups/public/</url>
....
We should use the same ID for repositories using the same URL even if one is in <repositories> and the other in <pluginRepositories>. That no added "-plugin" or "-plugins" in the repo ID.
In fact because of how Maven internally caches downloaded artifacts - tracking origin by repository ID - it may cause unnecessary pollution of local cache (Maven will download and store duplicate metadata files like maven-metadata-<id>.xml for the same artifacts). It also makes it harder to use mirror (you need to include both IDs in the mirror setting).
- is related to
-
JBEAP-31459 (8.1.z) Unable to build server sources when using different ID for repository and pluginRepository
-
- Coding In Progress
-
