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-archetypes.git


The following commit(s) were added to refs/heads/master by this push:
     new e5b19e2  Link the Testing Archetypes guide from the README
e5b19e2 is described below

commit e5b19e2e5a4c4df5d636b62a12483f7fe2d9b614
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sun Nov 1 09:59:57 2026 +0000

    Link the Testing Archetypes guide from the README
---
 README.md | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 79c6ebb..389f6ca 100644
--- a/README.md
+++ b/README.md
@@ -67,14 +67,10 @@ Testing the Archetypes
 ----------------------
 
 Every archetype module is tested by its `maven-archetype:integration-test` 
goal, which `mvn verify`
-runs. Each directory `src/test/resources/projects/<name>` is one test: it 
generates a project from the
-freshly built archetype and runs the goals in its `goal.txt` on the result.
-
-+ `archetype.properties` holds the generation parameters.
-+ `reference/` holds the expected generated project: every generated file 
needs a counterpart there,
-  and its content must match.
-+ `verify.groovy` checks the build result. `basedir` is the test directory, 
and the generated project
-  is in `project/<artifactId>` below it.
+runs. Each directory `src/test/resources/projects/<name>` is one test; the
+[Testing Archetypes 
guide](https://maven.apache.org/guides/mini/guide-testing-archetypes.html) 
describes
+its files (`archetype.properties`, `goal.txt`, `reference/`, `verify.groovy`) 
and how the goal compares
+the generated project with `reference/`.
 
 To test one archetype, run `mvn -B verify -pl maven-archetype-quickstart`. Add 
`-T2` to build modules in parallel;
 the archetype plugin is not marked thread-safe, so Maven warns about it.

Reply via email to