You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
bigdaz
changed the title
Add debug mode that prints each resolved dependency and associated configuration path
Log each resolved dependency and associated configuration path
Feb 11, 2024
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.
The text was updated successfully, but these errors were encountered: