Updated Branches: refs/heads/master e654f2f88 -> b0a886aff
moved explanations on Core ITs dependencies from README.md to site Project: http://git-wip-us.apache.org/repos/asf/maven-integration-testing/repo Commit: http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/b0a886af Tree: http://git-wip-us.apache.org/repos/asf/maven-integration-testing/tree/b0a886af Diff: http://git-wip-us.apache.org/repos/asf/maven-integration-testing/diff/b0a886af Branch: refs/heads/master Commit: b0a886affce2039dee4c53c54fea7de6214a8d0f Parents: e654f2f Author: Hervé Boutemy <[email protected]> Authored: Sun Dec 1 19:34:23 2013 +0100 Committer: Hervé Boutemy <[email protected]> Committed: Sun Dec 1 19:34:23 2013 +0100 ---------------------------------------------------------------------- README.md | 2 -- src/site/apt/index.apt | 17 +++++++++++++++++ 2 files changed, 17 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/maven-integration-testing/blob/b0a886af/README.md ---------------------------------------------------------------------- diff --git a/README.md b/README.md index 75c72bc..73a0328 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,3 @@ Maven Core Integration Tests Maven Developers List: [email protected] - -A little background to help understand things: 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 which obviously can't resolve anything. This setup using a file-based dummy repo also helps execution time because this repo produces (expected) 404s much faster than a HTTP-based repo. The one place where access to central is desired is in the MavenITBootstrapTest which doesn't really test anything but just primes the local repo with any artifacts the ITs will need. 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 what is populated during bootstraping. \ No newline at end of file http://git-wip-us.apache.org/repos/asf/maven-integration-testing/blob/b0a886af/src/site/apt/index.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/index.apt b/src/site/apt/index.apt index 5cc84da..8449fb8 100644 --- a/src/site/apt/index.apt +++ b/src/site/apt/index.apt @@ -15,3 +15,20 @@ Maven Core ITs * {{{./core-it-support/}Maven IT Support}}: Maven Integration Tests support tools, to completely decouple ITs from production plugins. * {{{./core-it-suite/}Maven ITs}}: The effective Maven Integration Tests suite. + + +* 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>>>, + 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>>> + ({{{./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. + + 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 + what is populated during bootstraping.
