From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Could this be related to <https://github.com/gradle/gradle/issues/21507>?

does a build scan show that dependency on the testRuntimeClasspath?

I have several projects on Gradle 8 and don’t see that dependency on testRuntimeClasspath, just the Junit 5 ones I’ve added.

I think its somehting different. The `dependencies` report reports correctly only one junit dependency

```+--- org.apache.logging.log4j:log4j-core:2.19.0
+--- net.java.dev.jna:jna:5.10.0
+--- co.elastic.logging:log4j2-ecs-layout:1.2.0
+--- co.elastic.logging:ecs-logging-core:1.2.0
+--- project :libs:elasticsearch-plugin-classloader
+--- com.carrotsearch:hppc:0.8.1
\--- project :test:framework
     +--- project :client:rest
     +--- com.carrotsearch.randomizedtesting:randomizedtesting-runner:2.8.0
     +--- junit:junit:4.12
     +--- org.hamcrest:hamcrest:2.1
     +--- org.apache.lucene:lucene-test-framework:9.5.0```

junit5 uses a different runner in the Test task

is this not the issue: `+--- junit:junit:4.12`

or is it that + `junit-4.13.2.jar` that is the issue?

the issue is that we have declared a dependency of junit:4.12 but we also get the junit13 on the classpath that is shipped with gradle itself. not even resolved from a repository or anything. so I would need to filter it out on the file level in some weired workaround I'd like to avoid. There shouldn't be `~/.gradle/wrapper/dists/gradle-8.0.1-all/aro4hu1c3oeioove7l0i4i14o/gradle-8.0.1/lib/junit-4.13.2.jar` on the classpath

yep.  odd.  alternatively, a workaround could be to remove junit 4.12 from the classpath via an exclude, which may be easier than removing the magically inserted 4.13.

Is this in 8.0 and 8.0.1? Also, what happens if you use the bin wapper, and not the all wrapper?

the only difference between bin and all wrapper should be the all wrapper includes sources and docs

I have a build scan for the problem available at <https://gradle.com/s/mt47vvnf7j7pm>. and I think I'm just creating a ticket as I havn't got a response from a gradle engineer yet

I'm just creating a ticket. I have a elasticsearch branch where it is reproducible

<@UABCKNV3K> I've created <https://github.com/gradle/gradle/issues/23995> with a simple reproduction description