From 0ef7f909b88726ff07f395af74b9421affc472ae Mon Sep 17 00:00:00 2001
From: Andy Wilkinson <awilkinson@pivotal.io>
Date: Wed, 13 May 2020 16:36:59 +0100
Subject: [PATCH] Disable generation of Gradle metadata for
 spring-boot-dependencies

Gradle's metadata for a platform does not provide a way to define
exclusions in the same way that can be done in <dependencyManagement>
in a Mavne bom. This means that Gradle 6 users lose the exclusions
that are defined in the pom as Gradle 6 will use the metadata rather
than the pom.

Until such a time as Gradle's metadata supports the configuration of
such exclusions we can avoid the problem by disabling the metadata's
publication.

Fixes gh-21350
---
 spring-boot-project/spring-boot-dependencies/build.gradle | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/spring-boot-project/spring-boot-dependencies/build.gradle b/spring-boot-project/spring-boot-dependencies/build.gradle
index 449b2ecce90..6f2c9510558 100644
--- a/spring-boot-project/spring-boot-dependencies/build.gradle
+++ b/spring-boot-project/spring-boot-dependencies/build.gradle
@@ -1847,3 +1847,7 @@ bom {
 		}
 	}
 }
+
+generateMetadataFileForMavenPublication {
+	enabled = false
+}