refreshVersions

End the dependency hell in minutes.

What

The refreshVersions plugin targets all kinds of Gradle projects, including the following:

Kotlin Multiplatform
Android
Kotlin/JS, Kotlin/JVM, Kotlin/Native
Java

The refreshVersions Gradle plugin brings the following benefits:

Centralizes dependencies versions (very useful in multi-module projects)
Shows available updates in seconds
Allows applying the available updates with minimal effort

Why (the problem this project solves)

Gradle multi-module projects are on the rise because of how it enforces code decoupling, which is a good thing for maintenance and inevitable changes.

Unfortunately, that means the number of build files (build.gradle[.kts]) are multiplied, which makes upgrading the dependencies versions where significantly more tedious as you now need to open, edit and check more files.

Also, some library vendors like Google are publishing artifacts with different versions (AndroidX, Google Play Services and Firebase, just to name a few). AndroidX for example has about 70 different families with different versions overall.

We saw this made developers to update the dependencies less and less often, effectively leading to legacy accumulation, or even projects abandon.

We firmly believe the modularization benefits should not be hindered by these drawbacks. That’s how refreshVersions was born.

We want discovery of dependencies updates to be as quick as possible, we want applying these updates be as quick as possible through the whole codebase, and we want to remove the human error factor in dependencies declaration and update. That’s exactly what refreshVersions can already do today in your project.

Usage

Adding to an existing project

Note: Only Gradle 6+ is supported at the moment, because it allows for simpler setup.

Updating Gradle is usually a good idea. You get fewer bugs, more features and more build speed, and it’s as simple as this:

$ ./gradlew wrapper --gradle-version 6.2.1

Step 1: Adding the plugin

Add the following snippet at the top your project’s root settings.gradle(.kts) file:

import de.fayard.dependencies.bootstrapRefreshVersionsAndDependencies

buildscript {
    repositories { gradlePluginPortal() }
    dependencies.classpath("de.fayard:dependencies:0.5.7")
}

bootstrapRefreshVersionsAndDependencies()

Step 2: Migrating the dependencies versions declaration place

Run the following command on the root project:

./gradlew migrateToRefreshVersionsDependenciesConstants --console=plain

This Gradle task is interactive. It will walk you through every module of your Gradle project, assisting you in replacing every hardcoded dependency version by the version placeholder (_) and an entry in the versions.properties file, for every configuration.

Note that while this Gradle task cannot break your build, it is experimental. We are aware its UX can be improved, and we have plans to work on it before the 1.0 release.

Find available updates (aka. refreshVersions)

Run the refreshVersions gradle task on the root project:

./gradlew refreshVersions

(It usually takes less than 10 seconds to execute on relatively big projects.)

Open the versions.properties file and see the available updates added as comments.

Apply updates

Applying updates is done in the versions.properties file.

Put the caret before or after the = symbol on the available update line.
Hold shift to start text selection, press the up arrow key and release shift.
Press the backspace/delete key.
If you’re in an IDE, sync Gradle changes to see new dependencies versions.

Bonus: tips for your Gradle projects

Good documentation can also help you upgrade an old project to the latest and greatest.

I have a series of articles called Built with Gradle:

To get the future tips and informative articles, you can follow me on dev.to.

Authors

FAQ

Questions? Look at the existing issues, then ask your own.

For special requests (not issues), you can also reach us out on Kotlin’s Slack

Release notes

See the CHANGELOG.md file.

Contributing

This project is licensed under the MIT License. See LICENSE.txt
Explain your use case and start the discussion before your submit a pull-request
CONTRIBUTING.md describes the process for submitting pull requests.

soyrros0x0 / refreshversions Goto Github PK