This message was deleted.

Is there a way to disable inheritance for the

testImplementation

configuration? I.e., it doesn't inherit the

implementation

dependencies.

configurations.implementation {
    setExtendsFrom(listOf())
}

Also, are there other test configurations that inherit from main configuration?

testRuntimeOnly

https://github.com/gradle/gradle/blob/master/platforms/jvm/plugins-java/src/main/java/org/gradle/api/plugins/JavaPlugin.java#L381-L382

You might be looking for the JVM Test Suite https://docs.gradle.org/current/userguide/jvm_test_suite_plugin.html, so you can define a custom test source with independent dependencies

I've not used JVM Test Suite, but that might be what I'm looking for. I want my unit tests to behave as if they're running from a separate module. The context is that when my unit tests compiles, I want to catch an

-Xlint:classfile

compilation warning(/error with

-Werror

) that would happen if I incorrectly made a dependency an

implementation

dependency instead of an

api

dependency. You won't see that warning/error when you run the unit tests, but you will see it when you try to use the types in that module from another module.

I will wager that bulk moving will be much easier than trying to hack around with excluding dependencies in Gradle 😅

I agree with Adam, that if you don't like the default behavior, easiest is to just use a different test suite. Otherwise you also need to check on Gradle updates whether something more is configured on the default test suite and need to adapt it. But currently what the

java

plugin does is setting • the compile classpath of the default test suite's source set to ◦ the output of the main source set ◦ and the default test suite's source set's compile classpath configuration • the runtime classpath of the default test suites's source set to ◦ the output of the default test suites's source set, ◦ the output of the main source set ◦ and the default test suite's source set's runtime classpath configuration • the default test suite's implementation configuration to extend from the main source set's implementation configuration • the default test suite's runtimeOnly configuration to extend from the main source set's runtimeOnly configuration If you want the behavior of custom test suites, you would need to revert those changes to their default settings, which I cannot tell you from the top of my head.