How to find/remove unused dependencies in Gradle

UPDATE: 28-06-2016: Android support to unused-dependency

In June, 2017, they have released the 4.0.0 version and renamed the root project name "gradle-lint-plugin" to "nebula-lint-plugin". They have also added Android support to unused-dependency.

In May 2016 Gradle has implemented the Gradle lint plugin for finding and removing unwanted dependency

Gradle Lint Plugin: Full Documentation

The Gradle Lint plugin is a pluggable and configurable linter tool for identifying and reporting on patterns of misuse or deprecations in Gradle scripts and related files.

This plugin has various rules. Unused Dependency Rule is one of them. It has three specific characteristics.

1. Removes unused dependencies.
2. Promotes transitive dependencies that are used directly by your codeto explicit first order dependencies.
3. Relocates dependencies to the 'correct' configuration.

To apply the rule, add:

gradleLint.rules += 'unused-dependency'

Details of Unused Dependency Rule is given in the last part.

To apply the Gradle lint plugin:

buildscript { repositories { jcenter() } }plugins {  id 'nebula.lint' version '0.30.2'}

Alternatively:

buildscript {  repositories { jcenter() }  dependencies {    classpath 'com.netflix.nebula:gradle-lint-plugin:latest.release'  }}apply plugin: 'nebula.lint'

Define which rules you would like to lint against:

gradleLint.rules = ['all-dependency'] // Add as many rules here as you'd like

For an enterprise build, we recommend defining the lint rules in a init.gradle script or in a Gradle script that is included via the Gradle apply from mechanism.

For multimodule projects, we recommend applying the plugin in an allprojects block:

allprojects {  apply plugin: 'nebula.lint'  gradleLint.rules = ['all-dependency'] // Add as many rules here as you'd like}

Details of Unused Dependency Rule is given in this part

To apply the rule, add:

gradleLint.rules += 'unused-dependency'

The rule inspects compiled binaries emanating from your project's source sets looking for class references and matches those references to the dependencies that you have declared in your dependencies block.

Specifically, the rule makes the following adjustments to dependencies:

1. Removes unused dependencies

• Family-style jars like com.amazonaws:aws-java-sdk are removed, asthey don't contain any code

2. Promotes transitive dependencies that are used directly by your code to explicit first order dependencies

• This has the side effect of breaking up family style JAR files, likecom.amazonaws:aws-java-sdk, into the parts that you are actuallyusing, and adding those as first order dependencies

3. Relocates dependencies to the 'correct' configuration

• Webjars are moved to the runtime configuration
• JAR files that don't contain any classes and content outside of META-INF aremoved to runtime
• 'xerces', 'xercesImpl', 'xml-apis' should always be runtime scoped
• Service providers (JAR files containing META-INF/services) likemysql-connector-java are moved to runtime if there isn't any provablecompile-time reference
• Dependencies are moved to the highest source set configurationpossible. For example, 'junit' is relocated to testCompile unlessthere is an explicit dependency on it in the main source set (rare).

UPDATE: Previous plugins

For your kind information, I want to share about previous plugins

1. The Gradle plugin that finds unused dependencies, declared and transitive is com.github.nullstress.dependency-analysis

But its latest version 1.0.3 is created 23 December 2014. After that there aren't any updates.

N.B: Many of our engineers are being confused about this plugin as they updated only the version number, nothing else.

The project mentioned in the earlier answers seem to be dead. I use gradle-dependency-analyze. Setup is simple:

buildscript {  repositories {    jcenter()  }  dependencies {    classpath 'ca.cutterslade.gradle:gradle-dependency-analyze:1.0.3'  }}apply plugin: 'ca.cutterslade.analyze'

Then do:

$ gradle analyzeDependencies

I've had a lot of luck using the Gradle Dependency Analysis Plugin. To get started with it, add the following two things to your Gradle build script.

buildscript {    repositories {        maven {            url "https://plugins.gradle.org/m2/"        }    }    dependencies {        classpath "com.github.nullstress:DependencyAnalysisPlugin:1.0.3"    }}

and

apply plugin: "dependencyAnalysis"

Once those are in place, run gradle analyze. If there are unused dependencies, you'll get a build failure that shows output similar to the text below, plus a list of the unused dependencies (both declared and transitive). The build failure is really handy if you want to enforce that there should be no unused dependencies via a CI build.

:foo:analyze FAILEDFAILURE: Build failed with an exception.* What went wrong:Execution failed for task ':foo:analyze'.> The project has unused declared artifacts