Skip to content
Go to file
This branch is 17 commits ahead, 6 commits behind 4finance:master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Build Status Coverage Status Gitter


The project has been forked since it has no longer been maintained at its original source. Also, since I'm the author of the majority of the code I have decided to migrate it to my organization.

Also I've dropped support for Gradle < 2.0


Just change





Gradle plugin that tells you what libs have new versions on Maven Central, so when you come back to a project, you know what you can update.

How it works?

You run the plugin:

gradle uptodate

And you get for example this:

New versions available:

How to install it?

Step 1: Add dependency to Maven Central and to the plugin

buildscript {
    repositories {	
    dependencies {
        classpath 'com.toomuchcoding:uptodate-gradle-plugin:+'

Step 2: Add the plugin to your build (

apply plugin: 'com.toomuchcoding.uptodate'

And now you can run the plugin with

gradle uptodate

How to configure which configurations should be checked for updates?

By default all project configurations are checked for updates but you can exclude any of them.

uptodate {
    excludeConfigurations 'providedCompile', 'providedRuntime'

If you want to check only specific configurations it's also possible, simply include those configurations.

uptodate {
    includeConfigurations 'compile'

Please note that excludes take precedence over includes.

How to exclude non-final versions from reported updates?

You can also provide patterns of versions that you would like to exclude. There are also some patterns (like BETA, RC, etc.) defined in com.toomuchcoding.uptodate.UptodatePluginExtension.VersionPatterns

By default following patterns are excluded: ALPHA, BETA, RC, CR, SNAPSHOT, MILESTONE, RELEASE( i.e. r08)

import static com.toomuchcoding.uptodate.VersionPatterns.*

uptodate {
    setExcludedVersionPatterns ALPHA, BETA, '.*-demo-?\\d*$'

You can also add your own patterns to the already excluded version patterns.

uptodate {
    addExcludedVersionPatterns '.*-demo-?\\d*$'

How to tune HTTP connections?

You can change connection timeout (5000 ms by default) and/or limit simultaneous HTTP connections (8 connections by default) by connectionTimeout and simultaneousHttpConnections properties respectively.

uptodate {
    connectionTimeout 10000
    simultaneousHttpConnections  4

How to run the plugin if you are behind an HTTP proxy?

The proxy settings can be configured by using one of the following approaches:

1. Via System properties (recommended)

Make sure to have the following properties configured when running the plugin:


2. Via plugin configuration

Add the proxyHostname, proxyPort (defaults to -1, which is the default port of the scheme) and proxyScheme (defaults to 'http') properties to the plugin configuration.

uptodate {
    proxyHostname 'localhost'
    proxyPort 15000
    proxyScheme 'http'

How to print project names along with information about new (or lack of) dependency updates?

By default (sub)project names are not printed so that you can easily operate on uptodate task output (e.g.: sort | uniq) but you can include project names in update headers by:

uptodate {
    reportProjectName true

How to break the build if new dependencies have been found?

You can add the possibility to break the build for new versions of dependencies by applying the following closure

uptodate {
    breakTheBuild {
        enabled = true

If turned on the default behaviour is such that if ANY new dependency is found then the build will be broken.

You can customize the inclusion and exclusion patterns by the following methods:

uptodate {
    breakTheBuild {
        enabled = true
        includePatterns('regex for dependency group or name to break the build if newer version is found', 'another regex')
        excludePatterns('regex for dependency group or name NOT to break the build if newer version is found', 'another regex')

To make the functionality available on demand you can apply for example a project property:

uptodate {
    breakTheBuild {
        enabled = project.hasProperty('uptodateBuildBreakingEnabled')

How to run the plugin on every build?

You can run the plugin automatically on every build, just by adding to your build.gradle

build.dependsOn 'uptodate'

But be warned, this will slow down the build by a few seconds (required to hit maven remote repo with http), so it is not suggested unless you don't care about build time.


To see what has changed in recent versions of Uptodate plugin see the CHANGELOG


Gradle plugin that tells you what libs have new versions on the specified Maven repository




No packages published
You can’t perform that action at this time.