You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by el...@apache.org on 2020/08/04 14:46:20 UTC
[maven-site] branch elharo-patch-7 created (now 4372b80)
This is an automated email from the ASF dual-hosted git repository.
elharo pushed a change to branch elharo-patch-7
in repository https://gitbox.apache.org/repos/asf/maven-site.git.
at 4372b80 grammar nit: subject verb agreement
This branch includes the following new commits:
new 4372b80 grammar nit: subject verb agreement
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[maven-site] 01/01: grammar nit: subject verb agreement
Posted by 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 4372b80a3c946fe92adaf1ab72ffecd9bafe35b4
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Tue Aug 4 10:46:14 2020 -0400
grammar nit: subject verb agreement
---
.../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 1c0167a..e94b5f7 100644
--- a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
+++ b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
@@ -126,8 +126,8 @@ Introduction to the Dependency Mechanism
[]
Although transitive dependencies can implicitly include desired dependencies, it is a good practice to explicitly
- specify the dependencies you are directly using in your own source code. This best practice proves its value especially
- when the dependencies of your project changes their dependencies.
+ specify the dependencies your source code uses directly. This best practice proves its value especially
+ when the dependencies of your project change their dependencies.
For example, assume that your project A specifies a
dependency on another project B, and project B specifies a dependency on project C. If you are directly using components