This is an automated email from the ASF dual-hosted git repository.
michaelo 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 48e0611 Update introduction-to-optional-and-excludes-dependencies.apt
48e0611 is described below
commit 48e061199cb9a98a6d23e4d07e476ea5152eb6a5
Author: younger50 <[email protected]>
AuthorDate: Tue Sep 3 18:47:52 2019 +0800
Update introduction-to-optional-and-excludes-dependencies.apt
fix typo
---
.../introduction/introduction-to-optional-and-excludes-dependencies.apt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
b/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
index 76f1ff9..d777110 100644
---
a/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
+++
b/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
@@ -125,7 +125,7 @@ Project-X -> Project-A
Since Maven resolves dependencies transitively, it is possible
for unwanted dependencies to be included in your project's classpath.
For example, a certain older jar may have security issues or be incompatible
with the Java
- version you're using. To address this, Maven allows you to exlude specific
dependencies.
+ version you're using. To address this, Maven allows you to exclude specific
dependencies.
Exclusions are set on a specific dependency in your POM, and are targeted
at a specific groupId and artifactId. When you build your project, that
artifact will not be added to your project's classpath <by way of the
