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

Author	SHA1	Message	Date
Brian Clozel	8fe21b8ef9	Build Antora docs as part of CI check job This commit adds the "antora" task to the check-project script in order to check for documentation failures when pushing to the current branch. The actual documentation is build is performed on the docs-build branch. Closes gh-30528	3 years ago
Brian Clozel	63e20404a2	Configure JDK 21 CI build This commit replaces the JDK 20 compatibility build with a JDK 21 (early access) variant. See gh-30339	3 years ago
Brian Clozel	8234fa2a13	Fix JDK20 env variable declaration in CI pipeline See gh-30185	3 years ago
Brian Clozel	e725e3a51b	Update Java versions and remove Java 18 build	3 years ago
Brian Clozel	6fd0615be9	Fix JDK18 declaration in CI pipeline See gh-27607	4 years ago
Brian Clozel	c0e479460e	Switch CI pipeline to a JDK17 baseline This commit introduces a new `spring-framework-6.0.x` CI pipeline with JDK 17 baseline. Note that Kotlin still uses a JDK11 baseline for now, this will be addressed in gh-27413. Closes gh-27409	4 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	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