This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-archetype.git


The following commit(s) were added to refs/heads/master by this push:
     new f288c630 Fix goal count, apt leftovers and obsolete FAQ entries in the 
plugin site
f288c630 is described below

commit f288c63057ff5a3d6a0995c14dd47a4611199e54
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sat Oct 31 17:09:26 2026 +0000

    Fix goal count, apt leftovers and obsolete FAQ entries in the plugin site
---
 .../src/site/markdown/archetype-repository.md      |  4 ++--
 maven-archetype-plugin/src/site/markdown/faq.md    | 22 +---------------------
 .../src/site/markdown/index.md.vm                  |  4 ++--
 3 files changed, 5 insertions(+), 25 deletions(-)

diff --git a/maven-archetype-plugin/src/site/markdown/archetype-repository.md 
b/maven-archetype-plugin/src/site/markdown/archetype-repository.md
index 4b5b508f..3c6a9de6 100644
--- a/maven-archetype-plugin/src/site/markdown/archetype-repository.md
+++ b/maven-archetype-plugin/src/site/markdown/archetype-repository.md
@@ -30,7 +30,7 @@ If you're not using a repository manager and the archetype is 
available at Maven
 
 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 with `archetype>> id 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 the id `archetype` to your 
`settings.xml` once:
 
 ```xml
 <settings>
@@ -38,7 +38,7 @@ Only in case of a third party archetype which is not managed 
by a repository you
     <mirror>
       <id>mrm-maven-plugin</id>
       <name>Mock Repository Manager</name>
-      <url>http://www.mycompany.com/maven-repository-manager</url>
+      <url>https://www.mycompany.com/maven-repository-manager</url>
       <mirrorOf>*,!archetype</mirrorOf>
     </mirror>
   </mirrors>
diff --git a/maven-archetype-plugin/src/site/markdown/faq.md 
b/maven-archetype-plugin/src/site/markdown/faq.md
index d0340abe..6a88c8d6 100644
--- a/maven-archetype-plugin/src/site/markdown/faq.md
+++ b/maven-archetype-plugin/src/site/markdown/faq.md
@@ -27,17 +27,13 @@ under the License.
 
 1. [What packaging should I use: `maven-archetype` or `jar`? What is the 
difference?](#packaging)
 1. [How to generate a project from an archetype in a custom (potentially 
authenticated) repository?](#authentication)
-1. [What is &quot;Old Archetype 1.0.x&quot;?](#old)
 1. [How do I get files like `.gitignore` included into my 
archetype?](#excludes)
 
 <a id="packaging"></a>
 
 ### What packaging should I use: `maven-archetype` or `jar`? What is the 
difference?
 
-`maven-archetype` packaging is available since 2.0-alpha-1: it should be used 
instead
-of `jar`, which was used for Old Archetype 1.0.x.
-
-Using `maven-archetype` packaging helps identifying archetypes in repositories 
and
+Use the `maven-archetype` packaging. It helps identify archetypes in 
repositories and
 adds archetype related bindings to build lifecycle: see
 [`maven-archetype` packaging documentation](../archetype-packaging/) for more
 information.
@@ -57,22 +53,6 @@ For resolving the **actual archetype** an artificial 
repository with id
 contained a repository (leveraging its URL). As fallback all regular remote
 repositories (as defined in the `settings.xml`) are tried.
 
-<a id="old"></a>
-
-### What is &quot;Old Archetype 1.0.x&quot;?
-
-Old Archetype 1.0.x was using a `archetype` XML descriptor defined in
-`/xsd/archetype-1.0.0.xsd`: see
-[old descriptor reference](/archetype/archetype-common/archetype.html).
-
-Archetype is now using `archetype-descriptor` XML descriptor defined in
-`/xsd/archetype-descriptor-1.1.0.xsd`: see
-[Archetype descriptor 
reference](/archetype/archetype-models/archetype-descriptor/archetype-descriptor.html).
-
-For compatibility, old archetypes can still be used to generate new projects, 
but
-archetypes should be updated to the new descriptor format: in the future, old 
format
-will be removed.
-
 <a id="excludes"></a>
 
 ### How do I get files like `.gitignore` included into my archetype?
diff --git a/maven-archetype-plugin/src/site/markdown/index.md.vm 
b/maven-archetype-plugin/src/site/markdown/index.md.vm
index 4b7200e2..65fdb81b 100644
--- a/maven-archetype-plugin/src/site/markdown/index.md.vm
+++ b/maven-archetype-plugin/src/site/markdown/index.md.vm
@@ -47,11 +47,11 @@ The Archetype Plugin is embedded in IDEs (Eclipse, 
NetBeans, IDEA).
 Goals Overview
 --------------
 
-The archetype plugin has four goals for direct use:
+The archetype plugin has three goals for direct use:
 
 - [archetype:generate](./generate-mojo.html) creates a Maven project from an 
archetype: asks the user to choose an archetype from the archetype catalog, and 
retrieves it from the remote repository. Once retrieved, it is processed to 
create a working Maven project.
 - [archetype:create-from-project](./create-from-project-mojo.html) creates an 
archetype from an existing project.
-- [archetype:crawl](./crawl-mojo.html) search a repository for archetypes and 
updates a catalog.
+- [archetype:crawl](./crawl-mojo.html) searches a repository for archetypes 
and updates a catalog.
 
 and three goals bound to default lifecycle by ['maven-archetype' 
packaging](../archetype-packaging/):
 

Reply via email to