Bukama commented on code in PR #1481: URL: https://github.com/apache/maven-site/pull/1481#discussion_r2596336324
########## content/markdown/guides/introduction/introduction-to-dependency-mechanism.md: ########## @@ -760,45 +760,53 @@ Starting from Maven 4.0, a new specific BOM packaging has been introduced. It al ## System Dependencies -`Important note: This is deprecated.` +`Important note: The usage of this scope is not recommended!` -Dependencies with the scope _system_ are not looked up in the Maven repository system. Instead the `dependency` element contains a `systemPath` pointing to a jar on the local file system. - -The system scope is commonly 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. A typical examples is the Java Authentication and Authorization Service (JAAS): +In rare occurrences it's needed to use a dependency which is not available in any repository, but only on local machine, for example a jar of some commercial application. +To include such a dependency in the build, the _system_ scope can be used. +Dependencies with the scope _system_ are not looked up in the Maven repository system. +Instead, the `dependency` element contains a `systemPath` pointing to a jar on the local file system. ```xml - <project xmlns="http://maven.apache.org/POM/4.0.0";> ... <dependencies> <dependency> - <groupId>javax.security</groupId> - <artifactId>jaas</artifactId> - <version>1.0.01</version> + <groupId>some.company</groupId> Review Comment: I want to have difference examples for a the originally use case for this dependency scope ("commerical/non public") and the JDK use case (public, but not at Central), which was the most common use case in the past, but is not necessary anymore as they are in Central nowadays. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
