Author: dennisl
Date: Sat Jun 14 05:41:39 2008
New Revision: 667792
URL: http://svn.apache.org/viewvc?rev=667792&view=rev
Log:
o Add version info about the 6th scope.
Modified:
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
Modified:
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt?rev=667792&r1=667791&r2=667792&view=diff
==============================================================================
---
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
(original)
+++
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
Sat Jun 14 05:41:39 2008
@@ -87,7 +87,7 @@
Dependency scope is used to limit the transitivity of a depedency, and also
to affect the classpath used for
various build tasks.
- There are 5 scopes available:
+ There are 6 scopes available:
* <<compile>>\
This is the default scope, used if none is specified. Compile dependencies
are available
@@ -112,7 +112,7 @@
which contains it explicitly. The artifact is always available and is not
looked up in a repository.
- * <<import>>\
+ * <<import>> <(only available in Maven 2.0.9 or later)>\
This scope is only used on a dependency of type <<<pom>>> in the
<<<\<dependencyManagement\>>>> section. It indicates that the specified
POM should be replaced with the dependencies in that POM's
<<<\<dependencyManagement\>>>> section. Since they are replaced,
dependencies with a scope of <<<import>>> do not actually participate in
limiting the transitivity of a dependency.
