Sam Brannen

Yes, the core Spring Framework project has used Gradle for its builds for several years.

Spring Boot historically used Maven for its build; however, the Spring Boot team recently migrated to Gradle. See the [Migrating Spring Boot's Build to Gradle](https://spring.io/blog/2020/06/08/migrating-spring-boot-s-build-to-gradle) blog for details.

> We could just stop using `SpringBootDependencyInjectionTestExecutionListener` as it doesn't appear to work as hoped or I think we need to rework the approach in a way that means we...

> That sounds great, Sam. Thanks. We'll be left with the problem described in this issue in 2.x, but with a much better path forward in 3.0. - See https://github.com/spring-projects/spring-framework/issues/28826

Since JUnit Jupiter 5.1, you can check the test instance lifecycle via `org.junit.jupiter.api.extension.ExtensionContext.getTestInstanceLifecycle()`.

I raised this issue to make us all aware of the fact that `ConditionEvaluationReport` support has been lost for Spring integration tests. However, I do not see this as a...

> Probably worth noting that `SpringBootDependencyInjectionTestExecutionListener` only outputs the report upon refresh failure and that, currently, it [doesn't work as intended](https://github.com/spring-projects/spring-boot/issues/24888). Ahhhh.... that's good to know. Thanks for sharing. I...

Putting this issue "on hold". After changing `AspectJHints` to the following... ```java @NativeHint(trigger = Assertions.class, initialization = { // Based on the native-image.properties in Byte Buddy // https://github.com/raphw/byte-buddy/blob/master/byte-buddy/src/main/resources/META-INF/native-image/net.bytebuddy/byte-buddy/native-image.properties @InitializationHint( packageNames...

I'll see if I can fit this in next week.

Please keep in mind that reporting features like display names and reporting entries (via a map of key-value pairs) will end up in the new reporting format from the Open...