Repository: maven-archetype Updated Branches: refs/heads/master 7002dde01 -> 44917e884
tried to improve explanations (and fix little typos) Project: http://git-wip-us.apache.org/repos/asf/maven-archetype/repo Commit: http://git-wip-us.apache.org/repos/asf/maven-archetype/commit/44917e88 Tree: http://git-wip-us.apache.org/repos/asf/maven-archetype/tree/44917e88 Diff: http://git-wip-us.apache.org/repos/asf/maven-archetype/diff/44917e88 Branch: refs/heads/master Commit: 44917e8849ff5a0157ecdcf704a6b3cb6bdcfa00 Parents: 7002dde Author: Hervé Boutemy <hbout...@apache.org> Authored: Sat May 20 11:08:10 2017 +0200 Committer: Hervé Boutemy <hbout...@apache.org> Committed: Sat May 20 11:08:10 2017 +0200 ---------------------------------------------------------------------- .../src/site/apt/archetype-repository.apt | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/maven-archetype/blob/44917e88/maven-archetype-plugin/src/site/apt/archetype-repository.apt ---------------------------------------------------------------------- diff --git a/maven-archetype-plugin/src/site/apt/archetype-repository.apt b/maven-archetype-plugin/src/site/apt/archetype-repository.apt index a9a2c83..f37beeb 100644 --- a/maven-archetype-plugin/src/site/apt/archetype-repository.apt +++ b/maven-archetype-plugin/src/site/apt/archetype-repository.apt @@ -26,23 +26,25 @@ ~~ NOTE: For help with the syntax of this file, see: ~~ http://maven.apache.org/doxia/references/apt-format.html - As of Maven Archetype Plugin 3.0.0 the archetype resolution has changed. It is not possible anymore to specify - the repository via the commandline, but instead the repositories as already specified for Maven are used. - This means that also the mirrors and proxies are respected, as well as the authentication on repositories. + As of Maven Archetype Plugin 3.0.0 the archetype resolution has changed: it is not possible anymore to specify + the repository via the command line (with <<<-DarchetypeRepository=repo.url>>>), but instead the repositories as + already defined for Maven are used. + This means also that the mirrors and proxies are respected, as well as the authentication on repositories. If you're not using a repository manager and the archetype is available at Maven Central, there's nothing you have to do. If you're using a repository manager and the archetype is available via this manager, there's nothing you have to do. - Only in case of a third party archetype which is not managed by a repository you have to add a repository entry to your <<<settings.xml>>> once: + Only in case of a third party archetype which is not managed by a repository you have to add a repository entry + with <<<archetype>> id to your <<<settings.xml>>> once: ---- ++---+ <settings> <mirrors> <mirror> <id>mrm-maven-plugin</id> <name>Mock Repository Manager</name> - <url>http://www.mycompany.com/maven-reporistory-manager</url> + <url>http://www.mycompany.com/maven-repository-manager</url> <mirrorOf>*,!archetype</mirrorOf> </mirror> </mirrors> @@ -62,7 +64,7 @@ <id>acme</id> <repositories> <repository> - <id>archetype</id> + <id>archetype</id><!-- id expected by maven-archetype-plugin to avoid fetching from everywhere --> <url>https://www.acme.com/repo</url> <releases> <enabled>true</enabled> @@ -77,5 +79,4 @@ </profile> </profiles> </settings> ---- - ++---+
