208 Commits (d5da9b070a416ea8b651bcd46a1b577e460ee933)

Author	SHA1	Message	Date
Andy Wilkinson	aefe52e4d0	Revert "Rework dep management to avoid consumers picking up strict constraints" ... This reverts commit b34a311d02 as, having disabled the publishing of Gradle's module metadata (4f75ab5), the changes are no longer needed. See gh-19609	5 years ago
Andy Wilkinson	4f75ab5f89	Disable generation of Gradle's module metadata ... The way in which we deploy the artifacts (publishing to a Maven repository on the filesystem and then using the Concourse artifactory resource to upload them) is incompatible with Gradle's module metadata generation. The metadata contains an entry, url, that contains the name of the artifact. This will be something like spring-boot-gradle-plugin-2.3.0.BUILD-20200114.095038-1.jar. The -1 in the name is derived from the Maven snapshot build number. It's -1 as the local repository to which the artifact is published is empty and has no maven-metadata.xml file. When the artifact is uploaded to Artifactory there is a maven-metadata.xml file so the build number is different. As a result, the module metadata points to a file that doesn't exist. This leads to problems like this when trying to consume the snapshots: Could not find spring-boot-gradle-plugin-2.3.0.BUILD-20200114.095038-1-2.3.0.BUILD-SNAPSHOT.jar (org.springframework.boot:spring-boot-gradle-plugin:2.3.0.BUILD-SNAPSHOT:20200114.101952-123) Gradle has used the maven-metadata.xml file on the server to determine that 2.3.0.BUILD-SNAPSHOT:20200114.101952-123 is the latest version. It has downloaded the .module file with this version but it points to spring-boot-gradle-plugin-2.3.0.BUILD-20200114.095038-1.jar. That file doesn't exist so the build fails. See gh-19609	5 years ago
Phillip Webb	862462b791	Update copyright year of changed files	5 years ago
Andy Wilkinson	b34a311d02	Rework dep management to avoid consumers picking up strict constraints ... Previously, enforcedPlatform dependencies were using to pull in the constraints defined in spring-boot-dependencies and spring-boot-parent and applied them strictly so that the constrained version had to be used. This worked as intended in Spring Boot's own build but incorrectly enforced those same strict version requirements on external consumers of Spring Boot's modules. This commit reworks how Spring Boot defines its internal dependency management so that platform dependencies are exposed to external consumers while enforced platform dependencies are using internally. See gh-19609	5 years ago
Vedran Pavic	8757f63360	Reuse optional configuration name constant ... See gh-19620	5 years ago
Vedran Pavic	57b7dfc730	Simplify Gradle's build settings ... See gh-19619	5 years ago
Andy Wilkinson	4b57884535	Remove outdated buildSrc README	5 years ago
Andy Wilkinson	ce99db1902	Port the build to Gradle ... Closes gh-19609 Closes gh-19608	5 years ago