spring-framework/buildSrc
Sam Brannen 36cd069c6e Exclude spring-jcl from nohttp check on main branch
The spring-jcl module no longer exists on main, but it still exists on
the 6.2.x branch and previous branches and can cause build failures when
switching between branches.
2025-01-27 15:33:43 +01:00
..
config/checkstyle Polish "Order modifiers to align with JLS" 2023-10-17 16:16:58 +02:00
src/main/java/org/springframework/build Exclude spring-jcl from nohttp check on main branch 2025-01-27 15:33:43 +01:00
README.md Add ArchUnit architecture checks 2025-01-17 17:21:10 +01:00
build.gradle Add ArchUnit architecture checks 2025-01-17 17:21:10 +01:00
gradle.properties Upgrade to spring-javaformat-checkstyle 0.0.42 2024-06-11 09:04:30 +02:00
settings.gradle Upgrade to Gradle Enterprise 3.2 2020-04-29 10:54:03 +02:00

README.md

Spring Framework Build

This folder contains the custom plugins and conventions for the Spring Framework build. They are declared in the build.gradle file in this folder.

Build Conventions

The org.springframework.build.conventions plugin applies all conventions to the Framework build:

  • Configuring the Java compiler, see JavaConventions
  • Configuring the Kotlin compiler, see KotlinConventions
  • Configuring testing in the build with TestConventions
  • Configuring the ArchUnit rules for the project, see org.springframework.build.architecture.ArchitectureRules

This plugin also provides a DSL extension to optionally enable Java preview features for compiling and testing sources in a module. This can be applied with the following in a module build file:

springFramework {
	enableJavaPreviewFeatures = true
}

Build Plugins

Optional dependencies

The org.springframework.build.optional-dependencies plugin creates a new optional Gradle configuration - it adds the dependencies to the project's compile and runtime classpath but doesn't affect the classpath of dependent projects. This plugin does not provide a provided configuration, as the native compileOnly and testCompileOnly configurations are preferred.

RuntimeHints Java Agent

The spring-core-test project module contributes the RuntimeHintsAgent Java agent.

The RuntimeHintsAgentPlugin Gradle plugin creates a dedicated "runtimeHintsTest" test task for each project. This task will detect and execute tests tagged with the "RuntimeHintsTests" JUnit tag. In the Spring Framework test suite, those are usually annotated with the @EnabledIfRuntimeHintsAgent annotation.

By default, the agent will instrument all classes located in the "org.springframework" package, as they are loaded. The RuntimeHintsAgentExtension allows to customize this using a DSL:

// this applies the `RuntimeHintsAgentPlugin` to the project
plugins {
	id 'org.springframework.build.runtimehints-agent'
}

// You can configure the agent to include and exclude packages from the instrumentation process.
runtimeHintsAgent {
	includedPackages = ["org.springframework", "io.spring"]
	excludedPackages = ["org.example"]
}

dependencies {
    // to use the test infrastructure, the project should also depend on the "spring-core-test" module
	testImplementation(project(":spring-core-test"))
}

With this configuration, ./gradlew runtimeHintsTest will run all tests instrumented by this java agent. The global ./gradlew check task depends on runtimeHintsTest.

NOTE: the "spring-core-test" module doesn't shade "spring-core" by design, so the agent should never instrument code that doesn't have "spring-core" on its classpath.