rfscholte commented on code in PR #191:
URL: https://github.com/apache/maven-site/pull/191#discussion_r1170360925
##########
content/apt/guides/introduction/introduction-to-dependency-mechanism.apt:
##########
@@ -174,9 +174,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.
Review Comment:
I'm missing some context: what was the reason to change the original text?
If we want to avoid the usecases, just explain how it works: a
`provided`-scoped artifact will be used from the local repository during
compile time, at runtime it is assumed to be there. A `system`-scoped artifact
should be available _on the system_ during both compile time and runtime.
--
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]
