You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by kw...@apache.org on 2024/03/08 12:57:54 UTC

(maven-site) branch feature/clarify-dep-mgmt-for-plugin-deps created (now a10d3aea)

This is an automated email from the ASF dual-hosted git repository.

kwin pushed a change to branch feature/clarify-dep-mgmt-for-plugin-deps
in repository https://gitbox.apache.org/repos/asf/maven-site.git


      at a10d3aea Clarify effect of depMgmt on plugin dependencies

This branch includes the following new commits:

     new a10d3aea Clarify effect of depMgmt on plugin dependencies

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: Clarify effect of depMgmt on plugin dependencies

Posted by kw...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

kwin pushed a commit to branch feature/clarify-dep-mgmt-for-plugin-deps
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit a10d3aea7709ebdea20bd44f97577f78a5dcac4d
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Fri Mar 8 13:57:45 2024 +0100

    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..fdc2d9ee 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) build 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 d4be9638..58c8e629 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