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 2026/08/03 21:38:36 UTC

(maven-assembly-plugin) branch master updated: [MASSEMBLY-958] Clarify dependency set resolution semantics (#1338)

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

elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-assembly-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new 60a79a69 [MASSEMBLY-958] Clarify dependency set resolution semantics (#1338)
60a79a69 is described below

commit 60a79a69d875c7ac5ea76ec18507433ebcac4fdf
Author: Václav Haisman <vh...@gmail.com>
AuthorDate: Mon Aug 3 23:38:31 2026 +0200

    [MASSEMBLY-958] Clarify dependency set resolution semantics (#1338)
---
 src/main/mdo/assembly-component.mdo | 4 +++-
 src/main/mdo/assembly.mdo           | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/src/main/mdo/assembly-component.mdo b/src/main/mdo/assembly-component.mdo
index c3e1f8de..f8ef7eda 100644
--- a/src/main/mdo/assembly-component.mdo
+++ b/src/main/mdo/assembly-component.mdo
@@ -387,7 +387,9 @@
       <version>1.0.0+</version>
       <description>
         A dependencySet allows inclusion and exclusion of project dependencies
-        in the assembly.
+        in the assembly. Dependency sets are evaluated against the project's
+        dependency graph after Maven dependency conflict resolution; include
+        patterns do not create separate dependency-resolution roots.
       </description>
       <fields>
         <field>
diff --git a/src/main/mdo/assembly.mdo b/src/main/mdo/assembly.mdo
index 0a9520bf..6b6f54dc 100644
--- a/src/main/mdo/assembly.mdo
+++ b/src/main/mdo/assembly.mdo
@@ -509,7 +509,9 @@
       <version>1.0.0+</version>
       <description>
         A dependencySet allows inclusion and exclusion of project dependencies
-        in the assembly.
+        in the assembly. Dependency sets are evaluated against the project's
+        dependency graph after Maven dependency conflict resolution; include
+        patterns do not create separate dependency-resolution roots.
       </description>
       <fields>
         <field>