Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix links (apt, not markdown), better split ITs vs support vs suite

This commit is contained in:
Hervé Boutemy 2022-01-16 15:11:36 +01:00
parent 6d5b007d19
commit 1d007733db
3 changed files with 42 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
its/core-it-suite/src/site/apt/bootstrap.apt.vm
View File

@ -29,8 +29,9 @@
Maven Core Integration Tests Bootstrap
Core IT Bootstrapping downloads from Central repository every dependency (artifacts, plugins) required to let
Core ITs Suite run without downloading anything later (see {{{./index.html}Core ITs Suite and dependencies}} rationale),
as defined in [a series of bootstrap projects](https://github.com/apache/maven-integration-testing/tree/master/core-it-suite/src/test/resources/bootstrap):
Core ITs Suite run without downloading anything later (see {{{./index.html#Core_ITs_Suite_and_Dependencies}Core ITs Suite and dependencies}} rationale).
Content to download is defined in {{{https://github.com/apache/maven-integration-testing/tree/master/core-it-suite/src/test/resources/bootstrap}a series of bootstrap projects}}:
%{toc|section=1|fromDepth=2}

35
its/core-it-suite/src/site/apt/index.apt.vm
View File

@ -31,41 +31,6 @@ Maven Core Integration Tests Suite
This module provides the {{{./testapidocs/org/apache/maven/it/package-summary.html}effective Core Integration Tests suite}},
starting with {{{./bootstrap.html}bootstrap}}.
* Running the Core ITs
By default, the project just packages the tests in an artifact. To actually run them, activate the <<<run-its>>> profile:
+----
mvn clean test -Prun-its
+----
This will subject the Maven version running the build to the integration tests.
If you would like to test a different Maven distribution, you can use the <<<mavenHome>>> system property to specify the
path of the Maven distribution to test:
+----
mvn clean test -Prun-its -DmavenHome=<maven-under-test>
+----
Alternatively, you can just specify the version of a previously installed/deployed Maven distribution which will be
downloaded, unpacked and tested:
+----
mvn clean test -Prun-its -DmavenVersion=2.2.1
+----
To run the ITs using embedded Maven 3.x, additionally activate the <<<embedded>>> profile.
ITs that don't require to fork Maven can also be run from the IDE using the Maven projects from the workspace if the
Maven dependencies are added to the test class path.
If you're behind a proxy, use the system properties <<<proxy.host>>>, <<<proxy.port>>>, <<<proxy.user>>>, <<<proxy.pass>>>
and <<<proxy.nonProxyHosts>>> to specify the required proxy setup for the ITs. Alternatively, set the system property
<<<maven.it.central>>> to a URL of a local repository manager (anonymous authentication only) that proxies the required
artifacts.
* Core ITs Suite Results
ITs results are displayed on the console and can be published in the site through Surefire Report.

42
its/src/site/apt/index.apt
View File

@ -31,8 +31,44 @@ Maven Core ITs
Maven Core Integration Tests provide tooling to test every aspect of Maven functionalities with any Maven version.
This project has declared the following modules:
This project is split in 2 modules:
* {{{./core-it-support/}Maven Core IT Support}}: Maven Integration Tests support tools, to completely decouple ITs from production plugins.
* {{{./core-it-support/}Maven Core IT Support}}: Maven Integration Tests support tools, to completely decouple ITs from production plugins,
* {{{./core-it-suite/}Maven Core ITs suite}}: The effective Maven Integration Tests suite.
* {{{./core-it-suite/}Maven Core ITs suite}}: The effective Maven Integration Tests suite, providing the interesting {{{./core-it-suite/surefire-report.html}tests results}}.
* Running the Core ITs
By default, the project just packages the tests in an artifact. To actually run them, activate the <<<run-its>>> profile:
+----
mvn clean test -Prun-its
+----
This will subject the Maven version running the build to the integration tests.
If you would like to test a different Maven distribution, you can use the <<<mavenHome>>> system property to specify the
path of the Maven distribution to test:
+----
mvn clean test -Prun-its -DmavenHome=<maven-under-test>
+----
Alternatively, you can just specify the version of a previously installed/deployed Maven distribution which will be
downloaded, unpacked and tested:
+----
mvn clean test -Prun-its -DmavenVersion=2.2.1
+----
To run the ITs using embedded Maven 3.x, additionally activate the <<<embedded>>> profile.
ITs that don't require to fork Maven can also be run from the IDE using the Maven projects from the workspace if the
Maven dependencies are added to the test class path.
If you're behind a proxy, use the system properties <<<proxy.host>>>, <<<proxy.port>>>, <<<proxy.user>>>, <<<proxy.pass>>>
and <<<proxy.nonProxyHosts>>> to specify the required proxy setup for the ITs. Alternatively, set the system property
<<<maven.it.central>>> to a URL of a local repository manager (anonymous authentication only) that proxies the required
artifacts.