Knowing the project(s) and configuration(s) that resolved a dependency is the first step in addressing dependency vulnerabilities. This can be difficult to determine in complex Gradle project. Build Scans and the dependency-resolution report can help, but these are not always the most convenient.

We should enable logging for the plugin that will print each resolved dependency together with the project and configuration that resolved it. A dependency resolved in multiple configurations will be printed multiple times.