Make spring-test available to compile classpath of consumers of spring-boot-test

[xenoterracide]

/home/xeno/.gradle/caches/modules-2/files-2.1/org.springframework.boot/spring-boot-test-autoconfigure/3.2.3/ea2e1778142fc8a05bd9325b433b13fe0a6845c1/spring-boot-test-autoconfigure-3.2.3.jar(/org/springframework/boot/test/autoconfigure/orm/jpa/DataJpaTest.class): warning: Cannot find annotation method 'value()' in type 'BootstrapWith': class file for org.springframework.test.context.BootstrapWith not found

not doing anything special here

@DataJpaTest
public class JpaAggregateTest {

since you're not using standard library definitions, maybe you need something like optionalApi either way the gradle metadata generated could be fixed by having this exposed as some kind of api. At least I think, the whole optional thing makes me uncertain of what's being generated for Gradle's metadata, and I'm not looking at that atm.

https://github.com/spring-projects/spring-boot/blob/main/spring-boot-project/spring-boot-test-autoconfigure/build.gradle#L34

[mhalbritter]

Hello! Do you happen to have a small reproducer for that?

[xenoterracide]

I can make something smaller than this if it's really necessary, just happens to be what I'm working on (so zero extra effort)

https://github.com/xenoterracide/spring-app-commons/actions/runs/8255489173/job/22582057132#step:5:102

https://github.com/xenoterracide/spring-app-commons/blob/cfa0776cca44671fca59cfd33a404c6512597d02/module/test-app/build.gradle.kts
https://github.com/xenoterracide/spring-app-commons/blob/cfa0776cca44671fca59cfd33a404c6512597d02/module/jpa/build.gradle.kts
https://github.com/xenoterracide/spring-app-commons/blob/cfa0776cca44671fca59cfd33a404c6512597d02/module/jpa/src/test/java/com/xenoterracide/jpa/JpaAggregateTest.java

note: the problem is in current main, and I probably won't "fix" it, but it's easier to ensure you can look at exactly what I have by sha.

[mhalbritter]

There's a lot going on in your project. The smallest possible reproducer would help to diagnose this.

[xenoterracide]

I actually think it could probably be more minimal than this, I don't think the multi-module is necessary, but it took me a bit to get to here. The java compiler diags are what emits this.

the commented out implementations if uncommented make these warnings go away, proving that api would work.

I found an additional thing whilst creating this reproducer. Although requiring/providing spring-test for spring-boot-test-autoconfigure seems reasonable. spring data commons seems less so.

./gradlew build or minimally ./gradlew testClasses will emit the warnings

demo.tar.gz

[mhalbritter]

Thanks for the reproducer! Any reason why you don't use

testImplementation("org.springframework.boot:spring-boot-starter-test")

instead of spring-boot-test-autoconfigure?

But besides that, I think we should expose the class Gradle complains about as an API dependency.

[xenoterracide]

transient dependency hell. Even if I used it, I set starters to "runtime only".

I've seen real world examples of people adding compile time dependencies on things that they shouldn't have, which made updates and refactors later harder. Starters make it easier to have this problem. Imagine the dependencies that have been removed from the spring stack since spring started, that have perhaps, accidentally ended up being a hard requirement because they were there and so used.

You should check this out https://github.com/autonomousapps/dependency-analysis-gradle-plugin

[wilkinsona]

This problem isn't specific to Gradle.

You can see a similar warning with Maven when configured with the appropriate compiler arg:

[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ gh-39901 ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 1 source file with javac [debug release 17] to target/test-classes
[WARNING] Cannot find annotation method 'value()' in type 'org.springframework.test.context.BootstrapWith': class file for org.springframework.test.context.BootstrapWith not found

This was generated from an app with this pom.xml:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>3.2.3</version>
		<relativePath/> <!-- lookup parent from repository -->
	</parent>
	<groupId>com.example</groupId>
	<artifactId>gh-39901</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>gh-39901</name>
	<description>Demo project for Spring Boot</description>
	<properties>
		<java.version>17</java.version>
	</properties>
	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-data-jpa</artifactId>
			<scope>runtime</scope>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-test-autoconfigure</artifactId>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.junit.jupiter</groupId>
			<artifactId>junit-jupiter</artifactId>
			<scope>test</scope>
		</dependency>
	</dependencies>

	<build>
		<plugins>
			<plugin>
				<groupId>org.springframework.boot</groupId>
				<artifactId>spring-boot-maven-plugin</artifactId>
			</plugin>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-compiler-plugin</artifactId>
				<configuration>
					<compilerArgs>
						<arg>-Xlint:classfile</arg>
					</compilerArgs>
				</configuration>
			</plugin>
		</plugins>
	</build>

</project>

It also contains a single test class annotated with @DataJpaTest.

That said, it's considerably less likely to occur with Maven as Maven does not separate the test compile classpath from the test runtime classpath. In the pom above, there's no spring-test dependency at all so the tests fail to run. Add a test-scoped dependency on spring-test removes the compiler warning and allows the tests to run.

But besides that, I think we should expose the class Gradle complains about as an API dependency

This is always tricky with optional dependencies. The most elegant solution to this problem is Gradle's feature variants. We haven't embraced them yet as there's no good equivalent on the Maven side so we're left with the optional approach for now.

In this case, when using optional dependencies as a solution, the question we have to answer is whether or not we think anyone should be using spring-boot-test-autoconfigure without spring-test. At the moment, the optional nature of its spring-test dependency means that we think the answer is yes. The knock-on effect of this is that anyone who wants to use a spring-test related feature of spring-boot-test-autoconfigure has to ensure that spring-test is on the classpath. For most people, spring-boot-starter-test achieves that but it doesn't help those who choose not to use it.

Looking through the public features of spring-boot-test-autoconfigure, I'm struggling to find one that doesn't require spring-test. This suggests that it should be a transitive dependency. We'd then have to decide if it should be a compile dependency or runtime dependency. Runtime would meet most people's needs, but not those compiling with -Xlint:classfile and striving to have no warnings.

We may want to perform a similar analysis of spring-boot-test as its spring-test dependency is also optional.