Apache/maven
1
0
Fork 0
mirror of https://github.com/apache/maven.git synced 2025-02-20 17:05:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

more links to bootstrap

Browse Source
This commit is contained in:
Hervé Boutemy 2019-08-04 18:59:31 +01:00
parent aaf5069c54
commit 1db7aa1193
3 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -28,8 +28,8 @@
Maven Core Integration Tests Bootstrap
Core IT Bootstrapping downloads from central repository every dependency (artifacts, plugins) required to let
ITs run without downloading anything later:
Core IT Bootstrapping downloads from Central repository every dependency (artifacts, plugins) required to let
ITs run without downloading anything later (see {{{../}Core ITs and dependencies}} rationale):
%{toc|section=1|fromDepth=2}

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

@ -40,15 +40,17 @@ Maven Core ITs
* Core ITs and dependencies
A good IT does not depend on external repos like central, it uses dedicated test plugins and test repositories.
The default <<<settings.xml>>> used by ITs helps to enforce this by pointing central at <<<file:target/null>>>,
A good IT does not depend on external repos like Central, it uses dedicated test plugins and test repositories.
The {{{https://github.com/apache/maven-integration-testing/blob/master/core-it-suite/src/test/resources-filtered/settings.xml}default <<<settings.xml>>>}}
used by ITs helps to enforce this by pointing <<<central>>> at <<<file:target/null>>>,
which obviously can't resolve anything. This setup using a file-based dummy repo also helps execution time,
because this repo produces (expected) <<<404>>>s much faster than a HTTP-based repo.
The one place where access to central is desired is in the <<<MavenITBootstrapTest>>>
The one place where access to Central is desired is in the <<<MavenITBootstrapTest>>>
({{{./core-it-suite/xref-test/org/apache/maven/it/MavenITBootstrapTest.html}src}},
{{{./core-it-suite/testapidocs/org/apache/maven/it/MavenITBootstrapTest.html}javadoc}}),
which doesn't really test anything but just primes the local repo with any artifacts the ITs will need.
which doesn't really test anything but just primes the local repo with any artifacts the ITs will need:
you can see {{{./core-it-suite/bootstrap.html}here}} the list of plugins and artifacts that are fetched during bootstrap.
So some care needs to be taken when introducing new dependencies into the ITs themselves or the support plugins.
Many times the failures that we encounter are discrepancies between actual artifact consumption required and

1
its/src/site/site.xml
View File

@ -35,6 +35,7 @@ under the License.
<item name="Introduction" href="index.html"/>
<!--item name="FAQ" href="faq.html"/-->
<item name="License" href="http://www.apache.org/licenses/"/>
<item name="Bootstrap" href="core-it-suite/bootstrap.html"/>
</menu>
<menu ref="modules"/>