This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git
The following commit(s) were added to refs/heads/master by this push:
new e1f0260fe Fix typo in configuring-classpath documentation
e1f0260fe is described below
commit e1f0260fe3e8349e893f9ffc5b3c0335dccc30b1
Author: Konrad Windszus <k...@apache.org>
AuthorDate: Mon Sep 22 18:13:45 2025 +0200
Fix typo in configuring-classpath documentation
---
.../src/site/apt/examples/configuring-classpath.apt.vm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/maven-surefire-plugin/src/site/apt/examples/configuring-classpath.apt.vm
b/maven-surefire-plugin/src/site/apt/examples/configuring-classpath.apt.vm
index ba1a8c7e8..b6060ddd1 100644
--- a/maven-surefire-plugin/src/site/apt/examples/configuring-classpath.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/examples/configuring-classpath.apt.vm
@@ -93,7 +93,7 @@ Additional Classpath Elements
override project dependencies or resources (except those which are filtered
with <<<classpathDependencyExclude>>>).
All artifacts of scope <<<compile>>> and <<<runtime>>> scope from the
dependency tree rooted in the given dependency are added.
The parametrization works like for regular
{{{https://maven.apache.org/pom.html#dependencies}Maven dependencies in a POM}}.
- {{{https://maven.apache.org/pom.html#exclusions}Exlusions}} are supported as
well.
+ {{{https://maven.apache.org/pom.html#exclusions}Exclusions}} are supported
as well.
Neither the dependency management section from the underlying POM is used
nor are the conflicts among the different dependency trees
(from the project dependencies or from the additional dependencies)
automatically resolved.
Conflicts lead to warnings, though, which help you clean up the classpath
manually.
