This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 5ea5710 Add missing word and tighten
5ea5710 is described below
commit 5ea5710b65d87e02c8a938d0d4ee3c4a487bfb3e
Author: Elliotte Rusty Harold <elh...@users.noreply.github.com>
AuthorDate: Tue Jan 29 06:55:26 2019 -0500
Add missing word and tighten
FYI, I'm tempted to delete this note completely since it describes a
situation that doesn't happen (compile+compile --> runtime), and I'm not sure a
typical user of Maven needs to think about this. They just need to know what
Maven does do, not what we sort of wish it could do.
---
.../apt/guides/introduction/introduction-to-dependency-mechanism.apt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
index 776ed11..853fd28 100644
--- a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
+++ b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
@@ -177,8 +177,8 @@ Introduction to the Dependency Mechanism
<<(*) Note:>>
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
+ 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.
* {Dependency Management}
