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-site.git
The following commit(s) were added to refs/heads/master by this push:
new ad8e8d52 [MNG-2496] Clarify effect of depMgmt on plugin dependencies
ad8e8d52 is described below
commit ad8e8d52b3b5a27c638af8a0c74d8e3de1d5255d
Author: Konrad Windszus <k...@apache.org>
AuthorDate: Fri Mar 8 13:57:45 2024 +0100
[MNG-2496] Clarify effect of depMgmt on plugin dependencies
Add section on depMgmt to POM reference
---
.../guides/introduction/introduction-to-dependency-mechanism.apt | 3 +++
content/apt/pom.apt.vm | 6 ++++++
2 files changed, 9 insertions(+)
diff --git
a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
index 27477b02..b63dc15b 100644
--- a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
+++ b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
@@ -475,6 +475,9 @@ Introduction to the Dependency Mechanism
[]
+ <<NOTE:>> The dependency management won't affect the (transitive)
dependencies of any <plugins>
+ used in the same effective POM but only the (transitive) project dependencies.
+
The reference information about the dependency management tags is available
from the
{{{../../ref/current/maven-model/maven.html#class_DependencyManagement}project
descriptor reference}}.
diff --git a/content/apt/pom.apt.vm b/content/apt/pom.apt.vm
index 3d4300f4..a62bd5cf 100644
--- a/content/apt/pom.apt.vm
+++ b/content/apt/pom.apt.vm
@@ -318,6 +318,12 @@ mvn install:install-file -Dfile=non-maven-proj.jar
-DgroupId=some.group -Dartifa
In the shortest terms, <<<optional>>> lets other projects know that, when
you use this project, you
do not require this dependency in order to work correctly.
+*** {Dependency Management}
+
+ Dependencies can be managed in the <<<dependencyManagement>>> section to
affect the resolution of dependencies
+ which are not fully qualified or to enforce the usage of a specific
transitive dependency version. Further information
+ in
{{{./guides/introduction/introduction-to-dependency-mechanism.html}Introduction
to the Dependency Mechanism}}.
+
*** {Dependency Version Requirement Specification}
Dependencies' <<<version>>> elements define version requirements, which are
used to compute dependency versions. Soft requirements can be replaced by
