You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/01/29 14:26:00 UTC

[jira] [Comment Edited] (ARCHETYPE-654) Clarify repository/server id used for custom repository catalog

    [ https://issues.apache.org/jira/browse/ARCHETYPE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811907#comment-17811907 ] 

Konrad Windszus edited comment on ARCHETYPE-654 at 1/29/24 2:25 PM:
--------------------------------------------------------------------

According to [https://github.com/apache/maven-archetype/blob/3a2b725198c3823fd5d7e9f88b665b2e4515a202/archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java#L86C31-L86C54] the repository id is
 # {{archetype}} / the mirror id for repo {{archetype}} or
 # {{central}} / the mirror id for repo {{central}}

That means that indeed the {{settings.xml}} would need to have an (enabled) repository with id {{archetype}} which would basically prevent using two different custom catalogs.


was (Author: kwin):
According to [https://github.com/apache/maven-archetype/blob/3a2b725198c3823fd5d7e9f88b665b2e4515a202/archetype-common/src/main/java/org/apache/maven/archetype/source/RemoteCatalogArchetypeDataSource.java#L86C31-L86C54] the repository id is
 # {{archetype }}/ the mirror id for repo {{archetype}} or
 # {{central / }}the mirror id for repo {{central}}

That means that indeed the {{settings.xml}} would need to have an (enabled) repository with id {{archetype}} which would basically prevent using two different custom catalogs.

> Clarify repository/server id used for custom repository catalog
> ---------------------------------------------------------------
>
>                 Key: ARCHETYPE-654
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-654
>             Project: Maven Archetype
>          Issue Type: Improvement
>          Components: Generator
>    Affects Versions: 3.2.1
>            Reporter: Konrad Windszus
>            Priority: Major
>
> 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 
> bq. {{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. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)