svn commit: r1838855 - in /maven/website/content: guides/introduction/introduction-to-dependency-mechanism.html maven-site-1.0-site.jar

[sv...@apache.org]

Author: svn-site-role
Date: Fri Aug 24 13:32:43 2018
New Revision: 1838855

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html
==============================================================================
--- maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html (original)
+++ maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html Fri Aug 24 13:32:43 2018
@@ -151,7 +151,7 @@ Karl Heinz Marbaise" />
         <div id="bodyColumn"  class="span10" >
 <div class="section">
 <h2><a name="Introduction_to_the_Dependency_Mechanism"></a>Introduction to the Dependency Mechanism</h2>
-<p>Dependency management is one of the features of Maven that is best known to users and is one of the areas where Maven excels. There is not much difficulty in managing dependencies for a single project, but when you start getting into dealing with multi-module projects and applications that consist of tens or hundreds of modules this is where Maven can help you a great deal in maintaining a high degree of control and stability.</p>
+<p>Dependency management is one of the features of Maven that is best known to users and is one of the areas where Maven excels. There is not much difficulty in managing dependencies for a single project; but when you work with multi-module projects and applications that consist of tens or hundreds of modules, Maven can help you a great deal in maintaining a high degree of control and stability.</p>
 <p>Learn more about:</p>
 <ul>
 <li><a href="#Transitive_Dependencies">Transitive Dependencies</a>
@@ -164,10 +164,10 @@ Karl Heinz Marbaise" />
 <li><a href="#System_Dependencies">System Dependencies</a></li></ul>
 <div class="section">
 <h3><a name="Transitive_Dependencies">Transitive Dependencies</a></h3>
-<p>Transitive dependencies are a new feature in Maven 2.0. This allows you to avoid needing to discover and specify the libraries that your own dependencies require, and including them automatically.</p>
+<p>Maven avoids the need to discover and specify the libraries that your own dependencies require by including transitive dependencies automatically.</p>
 <p>This feature is facilitated by reading the project files of your dependencies from the remote repositories specified. In general, all dependencies of those projects are used in your project, as are any that the project inherits from its parents, or from its dependencies, and so on.</p>
-<p>There is no limit to the number of levels that dependencies can be gathered from, and will only cause a problem if a cyclic dependency is discovered.</p>
-<p>With transitive dependencies, the graph of included libraries can quickly grow quite large. For this reason, there are some additional features that will limit which dependencies are included:</p>
+<p>There is no limit to the number of levels that dependencies can be gathered from. A problem arises only if a cyclic dependency is discovered.</p>
+<p>With transitive dependencies, the graph of included libraries can quickly grow quite large. For this reason, there are additional features that limit which dependencies are included:</p>
 <ul>
 <li><i>Dependency mediation</i> - this determines what version of a dependency will be used when multiple versions of an artifact are encountered. Currently, Maven 2.0 only supports using the &quot;nearest definition&quot; which means that it will use the version of the closest dependency to your project in the tree of dependencies. You can always guarantee a version by declaring it explicitly in your project's POM. Note that if two dependency versions are at the same depth in the dependency tree, until Maven 2.0.8 it was not defined which one would win, but since Maven 2.0.9 it's the order in the declaration that counts: the first declaration wins.
 <ul>

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.