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

Author	SHA1	Message	Date
Brian Clozel	21414bc265	Move Kotlin Gradle build config to convention This commit moves the Kotlin build configuration from the Gradle DSL to a dedicated convention in buildSrc.	3 years ago
Brian Clozel	6b0f6e9f27	Apply Gradle Test Retry plugin The plugin is configured to detect flaky tests and retry them 3 times when running on the CI, but still reports failures. This will provide a standard way to detect flaky tests as failures and successful attempts are shown in the tests report.	4 years ago
Brian Clozel	fc1408f827	Configure RuntimeHintsAgent in test suite This commit configures the `RuntimeHintsAgent` in the Spring Framework test suite. Instead of applying the agent to the entire test suite, and possibly interfering with other tests, this commit adds a new custom Gradle plugin that does the following: * create a new test task named `"runtimeHintsTest"` * run this task with the runtime hints java agent * only execute tests tagged with `"RuntimeHintsTests"` See gh-27981	4 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
陈其苗	fac1b94623	Fix typo in buildSrc/README.md See gh-24697	6 years ago
Sam Brannen	c91dd02905	Delete obsolete TestSourcesPlugin Since we have migrated to Gradle's built-in test fixture support, the custom TestSourcesPlugin Gradle plugin is now obsolete. See gh-23550	6 years ago
Brian Clozel	6008c61680	Use JApiCmp Gradle plugin for API diffs This commit removes JDiff from the Spring Framework build and instead, adds a Gradle plugin that configure JApiCmp tasks on the framework modules. Fixes gh-22942 See gh-23282	7 years ago
Brian Clozel	71ddb861bd	Move compile config to a Gradle convention This commit moves the compile configuration from the Gradle DSL to a convention. This configuration is not changing often, and we're using that opportunity to make the Java source compatibility a project property so as to easily recent JDKs this on the command line. See gh-23282	7 years ago