blob: a9a2c838052c59fb1b56b4196340687652318325 [file] [log] [blame]
Archetype Repository
Robert Scholte
~~ Licensed to the Apache Software Foundation (ASF) under one
~~ or more contributor license agreements. See the NOTICE file
~~ distributed with this work for additional information
~~ regarding copyright ownership. The ASF licenses this file
~~ to you under the Apache License, Version 2.0 (the
~~ "License"); you may not use this file except in compliance
~~ with the License. You may obtain a copy of the License at
~~ Unless required by applicable law or agreed to in writing,
~~ software distributed under the License is distributed on an
~~ KIND, either express or implied. See the License for the
~~ specific language governing permissions and limitations
~~ under the License.
~~ NOTE: For help with the syntax of this file, see:
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.
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:
<name>Mock Repository Manager</name>