This is all I'm getting from the report. It doesn't have any of the dependency packages that violate the rules, just a list of failed rules. I don't understand how this is useful. Is this a bug? How do I get the actual information about the violators in the report?

Rule Descriptions

Rule Name Description

1 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 2 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 3 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 4 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 5 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 6 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 7 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 8 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 9 duplicate-dependency-class classpaths with duplicate classes may break unpredictably depending on the order in which dependencies are provided to the classpath 10 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 11 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 12 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 13 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 14 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 15 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 16 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 17 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 18 overridden-dependency-version be declarative about first order dependency versions that are changed by conflict resolution 19 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 20 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 21 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 22 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 23 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 24 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 25 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 26 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 27 unused-dependency remove unused dependencies, relocate dependencies to the correct configuration, and ensure that directly used transitives are declared as first order dependencies 28 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 29 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 30 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 31 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 32 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 33 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 34 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 35 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 36 unused-exclude-by-conf excludes that have no effect on the classpath should be removed for clarity 37 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity 38 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity 39 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity 40 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity 41 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity 42 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity 43 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity 44 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity 45 unused-exclude-by-dep excludes that have no effect on the classpath should be removed for clarity

I just realized I was running an older version (6.8.0) checking if this is still an issue

Yes, still an issue in the latest.

Re-tested wit 0.8.1: unused-exclude-by-dep got better:

warning   unused-exclude-by-dep              the excluded dependency is not a transitive of com.google.gwt:gwt-dev:$gwtVersion, so has no effect
ui-api/build.gradle:49
exclude module:"commons-lang3"

But unused-dependency f.e. is still loosy in providing useful context:

warning   unused-dependency                  one or more classes in org.projectlombok:lombok:1.16.18 are required by your code directly (no auto-fix available)

@novaterata rules that have auto-fixes tend to not be descriptive, because they can be fixed automatically by fixGradleLint.

unused-dependency is a little confusing, because it currently covers used but undeclared as first order, as well as unused dependencies.

@DanielThomas fixGradleLint completely ravaged my project, I don't have time to figure out why. I just want to know which dependencies are unused

+1