Gradle 5: What's New, Release History & EOL Status

What Is New in Gradle 5

Gradle 5 introduces a major evolution focused on faster builds, better dependency management, and enhanced developer productivity. The release is packed with features that streamline the development workflow across JVM, native, and web projects.

How does Gradle 5 speed up my build?

Gradle 5 tackles build speed from multiple angles. The introduction of incremental annotation processing for Java means recompilations are faster when only annotation-generated code changes.

Build Cache support is now extended to Kotlin DSL script files. Caching the compiled build logic itself can shave off significant time in CI environments where the build script doesn't change often.

Gradle Module Metadata

This new, rich metadata format allows Gradle to make smarter dependency resolution decisions. It can avoid downloading unnecessary artifact variants, which cuts down network and disk I/O during dependency resolution.

What dependency management improvements should I use?

Dependency management gets more powerful and declarative. You can now define platform dependencies to manage consistent versions across a set of modules, similar to Maven's BOM.

Strict version constraints give you fine-grained control. You can declare a preferred version but enforce strict limits, preventing unwanted upgrades or downgrades.

dependencies {
    implementation('com.google.guava:guava:27.0.1-jre')
    constraints {
        implementation('com.google.guava:guava') {
            version {
                strictly('[27.0.1, 28.0.0[')
                prefer('27.0.1')
            }
        }
    }
}

Version ranges are now supported within dependency substitution rules, providing more flexibility when aligning or replacing dependencies in complex projects.

Is the Kotlin DSL ready for production?

Yes, Kotlin DSL 1.0 is a headline feature, marking it stable for production use. It offers improved editing experience with better IDE support, including content assist and navigation in IntelliJ IDEA and Android Studio.

The syntax is more concise and type-safe compared to Groovy. In practice, this means fewer runtime errors in your build scripts and easier refactoring.

plugins {
    java
    application
}

application {
    mainClassName = "com.gradle.sample.App"
}

Build Cache for Kotlin DSL scripts also improves performance, making the switch more practical for larger builds.

What breaking changes will affect my upgrade?

The most common impact is the final removal of the legacy compile and runtime configurations. You must migrate to implementation, api, runtimeOnly, and compileOnly.

Several deprecated properties and methods in the Tooling API have been removed. If you have custom tooling or IDE integrations, check the compatibility.

The --recompile-scripts option is gone. Use the --rerun-tasks option or clean your project if you need full re-execution.

What new tools help with project creation?

The gradle init command is significantly smarter. It can generate new projects with Kotlin DSL build scripts by default and offers more interactive options.

For library authors, init now supports generating multi-project builds with a Java library and a companion test suite project. This sets up a modern, reusable project structure out of the box.

You can specify the Gradle version directly when using the Wrapper: gradle wrapper --gradle-version=5.0. This simplifies automation scripts for setting up new projects.