Open dweiss opened 3 years ago
Related: https://github.com/palantir/gradle-consistent-versions/issues/308
I tried to force include the testFixtures
source set, but this can cause issues with mismatched versions:
versionsLock {
test {
from(sourceSets.testFixtures)
}
}
My current strategy is to make integrationTest
extend from test
, and then declare a testImplementation
dependency on every dependency in a testFixtures*
configuration. It's extremely unfortunate.
Hmm, the plugin will include all source sets with a name ending test
(case insensitive) e.g. test
and integrationTest
, but I suppose it would be reasonable to include those which start with test
as well. If you can rename testFixtures
to end with test
, that will unblock using existing versions.
The testFixtures*
configurations are from a core Gradle plugin, so not really an option for us. I do like the idea of looking for configurations starting with test
, since I (currently) can't think of any examples where you wouldn't want those included in the test version locks.
Dependencies in testFixturesApi (and other configurations), now standard, are not recognized and cause this: