svn commit: r1852634 - 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: Thu Jan 31 19:41:47 2019
New Revision: 1852634

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 Thu Jan 31 19:41:47 2019
@@ -223,7 +223,7 @@ Karl Heinz Marbaise" />
 <td align="left">-</td>
 <td align="left">test</td>
 <td align="left">-</td></tr></table>
-<p><b>(*) Note:</b> it is intended that this should be runtime scope instead, so that all compile dependencies must be explicitly listed - however, there is the case where the library you depend on extends a class from another library, forcing you to have available at compile time. For this reason, compile time dependencies remain as compile scope even when they are transitive.</p></div>
+<p><b>(*) Note:</b> it is intended that this should be runtime scope instead, so that all compile dependencies must be explicitly listed. However, if a library you depend on extends a class from another library, both must be available at compile time. For this reason, compile time dependencies remain as compile scope even when they are transitive.</p></div>
 <div class="section">
 <h3><a name="Dependency_Management">Dependency Management</a></h3>
 <p>The dependency management section is a mechanism for centralizing dependency information. When you have a set of projects that inherits a common parent it's possible to put all information about the dependency in the common POM and have simpler references to the artifacts in the child POMs. The mechanism is best illustrated through some examples. Given these two POMs which extend the same parent:</p>

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