[ARCHETYPE-654] Clarify repository/server id used for custom repository catalog

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 3.3.0
• Component/s: Generator
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 29/Jan/24 14:03
• Updated: 07/Feb/24 17:55
• Resolved: 07/Feb/24 17:55

Description

According to https://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html#archetypeArtifactId a repository with id archetype can be used to resolve catalogs from a remote repository. The same id is supposed to be used in case that repo uses authentication. This contradicts the FAQ entry at https://maven.apache.org/archetype/maven-archetype-plugin/faq.html#authentication which states that the id is supposed to be <archetypeArtifactId>-repo which would require one server section per archetype in a repo requiring authentication.

Also it is unclear which value archetypeArtifact should be set to to consider the catalog from a specific remote repository as

remote is the shortcut for Maven Central repository or its mirror.

But in case there is no mirror for Maven Central but rather a dedicated catalog of custom archetypes maintained in a a custom repo the value is unclear.

Also adding a repository with id archetype to settings would not only affect m-archetype-p but every resolution with Maven.

Issue Links

• is related to: ARCHETYPE-528 Archetype:generate from repos besides central does not work
• relates to: ARCHETYPE-655 Get rid of Wagon API to download catalogs
• links to: GitHub Pull Request #185