Tree: fb1f0eccfb

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'fb1f0eccfb'

${ noResults }

Commit Graph

2 Commits (fb1f0eccfb872c045ce3ed00a5c15c8e6fbbd832)

Author	SHA1	Message	Date
Stephane Nicoll	2c2464b1e7	Make script executable	5 years ago
Stephane Nicoll	865969400b	Polish ... See gh-26882	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
Brian Clozel	60725294e2	Only run checks in pipelines with JDK variants ... This commit updates the build pipeline to only run the checks (formatting and tests) with the build when non-JDK8 variants are used for sanity checks. See gh-22490	6 years ago