GitHub-Spring/spring-framework - spring-framework - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Brian Clozel	92b2b828f5	Fix Java 17 test CI and remove Java 11 variant This commit fixes configuration and runtime issues with the Java 17 test CI variant and removes the Java 11 one, now that Spring Framework 5.3.x is in maintenance mode.	3 years ago
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	5 years ago
Sam Brannen	d30432b6c0	Fix syntax in toolchains example See gh-25787	5 years ago
Brian Clozel	85eb589c2e	Fix Gradle Java Toolchain configuration This commit fixes various issues with the configuration of the Gradle Java toolchain in the build. First, the configuration of build properties is fixed in the CI pipeline because it wasn't properly checked. The JMH plugin is also upgraded and we now configure its toolchain support. This commit also rewrites the XJC tasks in the spring-oxm module, leveraging a Gradle plugin that creates actual compile tasks we can configure. See gh-25787	5 years ago
Brian Clozel	3ab39eda08	Fix Gradle Toolchain configuration See gh-25787	5 years ago
Brian Clozel	a8d553218c	Introduce Gradle Toolchain support in build Prior to this commit, the Spring Framework build would rely on setting a custom Java HOME for building all sources and tests with that JDK. This approach is not flexible enough, since we would be testing the source compatibility against a recent JDK, but not a common case experienced by the community: compiling and running application code with a recent JDK and the official, JDK8-based Framework artifacts. This method is also limiting our choice of JDKs to the ones currently supported by Gradle itself. This commit introduces the support of Gradle JVM Toolchains in the Spring Framework build. We can now select a specific JDK for compiling the main SourceSets (Java, Groovy and Kotlin) and another one for compiling and running the test SourceSets: `./gradlew check -PmainToolChain=8 -PtestToolchain=15` Gradle will automatically find the JDKs present on the host or download one automcatically. You can find out about the ones installed on your host using: `./gradlew -q javaToolchains` Finally, this commit also refactors the CI infrastructure to: * only have a single CI image (with all the supported JDKs) * use this new feature to compile with JDK8 but test it against JDK11 and JDK15. Closes gh-25787	5 years ago