[maven-site] 01/01: docs: system dependencies are not always available

[el...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

elharo pushed a commit to branch elharo-patch-7
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit 06a0dd6aa86db082f364c5e6fc54a783c3f8eed2
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Tue Aug 4 15:45:24 2020 -0400

    docs: system dependencies are not always available
    
    @michael-o
---
 .../introduction-to-dependency-mechanism.apt           | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
index e94b5f7..61a3eb4 100644
--- a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
+++ b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
@@ -172,9 +172,10 @@ Introduction to the Dependency Mechanism
    unit tests (src/test/java) but not in the model code (src/main/java).
 
  * <<system>>\
-   This scope is similar to <<<provided>>> except that you have to provide the JAR
-   which contains it explicitly. The artifact is always available and is not
-   looked up in a repository.
+   Maven does not add system-scoped dependencies to any classpath.
+   A system scoped dependency must be added to the classpath by means 
+   outside of Maven; for example, by placing its jar in the jre/lib/ext
+   directory of the virtual machine. The artifact is not looked up in a repository.
 
  * <<import>>\
    This scope is only supported on a dependency of type <<<pom>>> in the <<<\<dependencyManagement\>>>> section. It
@@ -822,12 +823,11 @@ Introduction to the Dependency Mechanism
 
  <<<Important note: This is deprecated.>>>
 
- Dependencies with the scope <system> 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
+ Dependencies with the scope <system> are not looked up in the Maven repository system.
+ They are usually used to tell Maven about dependencies provided by the JDK or the VM. 
+ 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).
 
  A simple example would be: