In your Android projects, you likely have many dependencies in your Gradle files. Updates often provide bugfixes or new features that you want to include in your app. However, checking for updates is not integrated by default. There is a solution though. Ben Manes wrote a Gradle Versions Plugin that does the work for you. To get started, add the buildscript dependency to your project’s gradle.build file and apply the plugin:
apply plugin: 'com.github.ben-manes.versions' buildscript { repositories { jcenter() } dependencies { classpath 'com.android.tools.build:gradle:1.3.1' classpath 'com.github.ben-manes:gradle-versions-plugin:0.11.3' } }
Simple as that. Now you have a new gradle task dependencyUpdates to check for updated dependencies in your project.
For convenience, you can add a new Configuration via Run > Edit Configurations. When adding, choose Gradle as type and configure as shown in the picture, after selecting your Gradle project:
Now you can choose the Check dependencies configuration and run it.
After the task completes, a report is shown in the Gradle console, telling you which dependencies have updates ready for you to explore:
------------------------------------------------------------ : Project Dependency Updates (report to plain text file) ------------------------------------------------------------ The following dependencies are using the latest integration version: - backport-util-concurrent:backport-util-concurrent:3.1 - backport-util-concurrent:backport-util-concurrent-java12:3.1 The following dependencies exceed the version found at the integration revision level: - com.google.guava:guava [99.0-SNAPSHOT <- 16.0-rc1] - com.google.guava:guava-tests [99.0-SNAPSHOT <- 16.0-rc1] The following dependencies have later integration versions: - com.google.inject:guice [2.0 -> 3.0] - com.google.inject.extensions:guice-multibindings [2.0 -> 3.0]