Closed nmatt closed 6 days ago
A workaround is to exclude the transitive test dependencies via dependency exclusions in the dependency declaration of the direct test dependency, but that's significant work to maintain, and is also error prone (when a transitive test dependency turns into a non-test dependency later).
Okay, I may have mistaken the behavior after all, closing for the time being.
When using deep scan, transitive dependencies with scope "test" are checked and can lead to conflicts, although those dependencies aren't relevant for the testing of the current project. The expected behavior would be to only consider direct dependencies having scope "test", and to ignore transitive dependencies having scope "test" regardless of the plugin's scope setting.