tronku / dependency-analysis-android-gradle-plugin Goto Github PK

The Dependency Analysis Gradle Plugin (née Dependency Analysis Android Gradle Plugin) detects the following:

1. Unused dependencies.

2. Used transitive dependencies (which you may want to declare directly).

3. Dependencies declared on the wrong configuration (api vs implementation vs compileOnly, etc.).

4. Unnecessary plugins (currently only kapt).

As a side effect, the plugin can also tell you your project’s ABI, and produces graphviz files representing various views of your dependency graph, among other things. These side effects are currently mostly undocumented internal behaviors, but they may be interesting for some advanced users.

For detailed instructions, see the wiki

The simplest approach is to add the following:

For a quick start, just run the following:

At time of writing, there are two distinct models available for conducting dependency analysis. By default, from version 1.0.0-rc01, the plugin uses the "new model." With that version, you may switch to the "old model" via the system property dependency.analysis.old.model=true. That is also the final version of the plugin that support use of the old model. From 1.0.0-rc02, the old model is no longer available.

The following is a list of articles / blog posts that have been published discussing this plugin:

1. The proper care and feeding of your Gradle build

2. Dependency Analysis Gradle Plugin: Using bytecode analysis to find unused dependencies

3. Dependency Analysis Gradle Plugin: What’s an ABI?

4. Reducing my Gradle plugin’s impact on configuration time: A journey

…​with more to come :)

This plugin has also been featured in these newsletters:

1. Gradle, September 2020

2. Gradle, August 2020

3. Android Weekly, Issue #423

4. Gradle, July 2020

5. Gradle, June 2020