Sam Brannen 38b592444d Store resolved toolchain info as custom values in build scan ... Prior to this commit, we registered custom values in the build scan for the main and test toolchains based on input values provided via the mainToolchain and testToolchain project properties. Beginning with this commit, the custom values we register are based on the available metadata for the resolved JDK/JVM for each toolchain. For example, instead of registering the following custom value... Test toolchain : JDK11 ... we now register the following which includes the vendor, version, and installation path of the JDK/JVM. Test toolchain : AdoptOpenJDK 11 (/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home) Once Gradle's JavaInstallationMetadata includes the exact version, we will likely use that instead of the installation path. See gh-25787		2021-05-05 15:19:27 +02:00
..
wrapper	Upgrade to Gradle 6.8.3	2021-02-22 23:00:49 +01:00
docs.gradle	Upgrade reference docs dependencies	2020-12-08 11:38:39 +01:00
ide.gradle	Remove Eclipse resource filter for 'build' folder	2021-05-04 11:36:21 +02:00
publications.gradle	Remove artifactory plugin from build	2020-04-28 14:34:40 +02:00
spring-module.gradle	Fix Gradle Java Toolchain configuration	2021-05-03 15:02:09 +02:00
toolchains.gradle	Store resolved toolchain info as custom values in build scan	2021-05-05 15:19:27 +02:00