Add information about non transitive test dependencies.
git-svn-id: https://svn.apache.org/repos/asf/maven/site/trunk@1748887 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
index aff297c..2bb46a3 100644
--- a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
+++ b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
@@ -3,8 +3,10 @@
------
Brett Porter
Trygve Laugstol
+ Karl Heinz Marbaise
------
2005-10-12
+ 2016-06-17
------
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -125,7 +127,7 @@
* <<test>>\
This scope indicates that the dependency is not required for normal use of the application, and
- is only available for the test compilation and execution phases.
+ is only available for the test compilation and execution phases. This scope is not transitive.
* <<system>>\
This scope is similar to <<<provided>>> except that you have to provide the JAR
@@ -768,6 +770,8 @@
* {System Dependencies}
+ <<<Important note: This is marked deprecated.>>>
+
Dependencies with the scope <system> are always available and are not looked
up in repository. They are usually used to tell Maven about dependencies which
are provided by the JDK or the VM. Thus, system dependencies are especially
diff --git a/content/apt/pom.apt b/content/apt/pom.apt
index efae248..9fe53d9 100644
--- a/content/apt/pom.apt
+++ b/content/apt/pom.apt
@@ -4,7 +4,7 @@
Eric Redmond, et al.
Karl Heinz Marbaise
-----
- 2015-10-13
+ 2016-06-17
-----
POM Reference
@@ -374,7 +374,7 @@
It is in the runtime and test classpaths, but not the compile classpath.
* <<test>> - this scope indicates that the dependency is not required for normal use of the application, and
- is only available for the test compilation and execution phases.
+ is only available for the test compilation and execution phases. It is not transitive.
* <<system>> - this scope is similar to <<<provided>>> except that you have to provide the JAR which contains
it explicitly. The artifact is always available and is not looked up in a repository.
