Hi Bill, We are using a Gradle plug-in to identify dependencies that are unused, or are declared in the wrong module or scope. This is called out by the Gradle documents on improving build [ https://guides.gradle.org/performance/#avoid_unnecessary_and_unused_dependencies]. The plug-in documentation is here [ https://github.com/nebula-plugins/gradle-lint-plugin/wiki/Unused-Dependency-Rule ]
Thank you, -Robert Houghton On Fri, Sep 28, 2018 at 10:18 AM Bill Burcham <bburc...@pivotal.io> wrote: > From the PR, Anthony, it seems to me that Patrick is proposing that each > build.gradle be explicit about mentioning the "things" it depends on. For > example: > > [image: image.png] > > Look at how geode-connectors goes from mentioning a few dependencies to > mentioning many more. The value of this is that it ostensibly shows us all > the things that geode-connectors actually depends on. > > The challenge I see is two-fold: > > • as with Java imports and "unused imports", there is the risk of listing > more dependencies than we actually need > • there's also the risk that we still don't have a complete list of > dependencies > > Patrick: do you have tool support for this? Is there a tool that can > identify or even remove unused dependencies? What process do you use for > finding these heretofore hidden dependencies? Did you run gradle > app:dependencies? >
