[
https://issues.apache.org/jira/browse/ARCHETYPE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated ARCHETYPE-654:
--------------------------------------
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
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.
was:
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.
> 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)
