svn commit: r1880158 - 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: Wed Jul 22 17:00:26 2020
New Revision: 1880158

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 Wed Jul 22 17:00:26 2020
@@ -720,7 +720,7 @@ Karl Heinz Marbaise" />
 <li>When referring to artifacts whose poms have transitive dependencies the project will need to specify versions of those artifacts as managed dependencies. Not doing so will result in a build failure since the artifact may not have a version specified. (This should be considered a best practice in any case as it keeps the versions of artifacts from changing from one build to the next).</li></ul></section></section><section>
 <h3><a name="System_Dependencies">System Dependencies</a></h3>
 <p><code>Important note: This is deprecated.</code></p>
-<p>Dependencies with the scope <i>system</i> 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 useful for resolving dependencies on artifacts which are now provided by the JDK, but were available as separate downloads earlier. Typical example are the JDBC standard extensions or the Java Authentication and Authorization Service (JAAS).</p>
+<p>Dependencies with the scope <i>system</i> 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 useful for resolving dependencies on artifacts which are now provided by the JDK, but were available as separate downloads earlier. Typical examples are the JDBC standard extensions or the Java Authentication and Authorization Service (JAAS).</p>
 <p>A simple example would be:</p>
 <div class="source"><pre class="prettyprint linenums">
 &lt;project&gt;

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