Author: schulte
Date: Tue Nov 15 00:21:33 2016
New Revision: 1769704
URL: http://svn.apache.org/viewvc?rev=1769704&view=rev
Log:
o Improved the wording of the dependency management import feature description.
I read this when preparing the 3.4.0 release notes for MNG-5971 and it
makes me 100% confident that the fix for MNG-5971 really is making the
dependency management import feature behave as it got documented nearly
a decade ago.
Modified:
maven/site/trunk/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
Modified:
maven/site/trunk/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt?rev=1769704&r1=1769703&r2=1769704&view=diff
==============================================================================
---
maven/site/trunk/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
(original)
+++
maven/site/trunk/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
Tue Nov 15 00:21:33 2016
@@ -135,9 +135,10 @@ Introduction to the Dependency Mechanism
looked up in a repository.
* <<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.
+ This scope is only supported on a dependency of type <<<pom>>> in the
<<<\<dependencyManagement\>>>> section. It
+ indicates the dependency to be replaced with the effective list of
dependencies in the specified 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.
[]
