Document exclude potential breaking change

Issue #17964
gradle · Aug 31, 2021 · e5c5f49 · e5c5f49
1 parent d37a0b0
commit e5c5f49
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/subprojects/docs/src/docs/release/notes.md b/subprojects/docs/src/docs/release/notes.md
@@ -31,7 +31,7 @@ For Java, Groovy, Kotlin and Android compatibility, see the [full compatibility
 
 <!-- Do not add breaking changes or deprecations here! Add them to the upgrade guide instead. --> 
 
-<!-- 
+<!-- `
 
 ================== TEMPLATE ==============================
 

diff --git a/subprojects/docs/src/docs/userguide/migration/upgrading_version_7.adoc b/subprojects/docs/src/docs/userguide/migration/upgrading_version_7.adoc
@@ -45,6 +45,12 @@ and depended on how a plugin was added to the class path. Now the plugins are al
 in the same order they are declared in the `plugins` block which in rare cases might change
 behavior of existing builds.
 
+==== Effects of exclusion on substituted dependencies in dependency resolution
+
+Prior to this version, a dependency substitution target could not be excluded from a dependency graph.
+This was caused by checking for exclusions prior to performing the substitution.
+Now Gradle will also check for exclusion on the substitution result.
+
 [[changes_7.2]]
 == Upgrading from 7.1 and earlier