Search code, repositories, users, issues, pull requests...

This is a patch release for Gradle 6.2.

This fixes a critical bug in Gradle 6.2:

Multi-project build use the properties of the rootProject for all included builds. #12381

We recommend that you use Gradle 6.2.2 over the initial release of Gradle 6.2.

Upgrade Instructions

Switch your build to use Gradle 6.2.2 by updating your wrapper:

./gradlew wrapper --gradle-version=6.2.2

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.2.2.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

`v6.2.1`

This is a patch release for Gradle 6.2.

This fixes several critical bugs in Gradle 6.2:

Project name disambiguation causes project / external dependency conflicts to be missed. #12315
IdeaModelBuilder does not provide groovy-all as compile dep for buildSrc #12274
Gradle crashes if GRADLE_RO_DEP_CACHE is set and it cannot create modules-2 directory within it #12293

We recommend that you use Gradle 6.2.1 over the initial release of Gradle 6.2.

Upgrade Instructions

Switch your build to use Gradle 6.2.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.2.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.2.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

`v6.2.0`

The Gradle team is excited to announce Gradle 6.2.

We would like to thank the following community contributors to this release of Gradle:

Stefan Neuhaus,
EthanLozano,
Pavlos-Petros Tournaris,
Márton Braun,
Thomas Iguchi,
Vladimir Sitnikov,
Peter Stöckli,
Sebastian Schuberth,
Frieder Bluemle,
ColtonIdle,
and Roberto Perez Alcolea.

Upgrade Instructions

Switch your build to use Gradle 6.2 by updating your wrapper:

./gradlew wrapper --gradle-version=6.2

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.2.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

`v6.1.1`

This is a patch release for Gradle 6.1.

This fixes several critical bugs in Gradle 6.1:

Plugins using kotlin-dsl and compiled with 6.1 are incompatible with Gradle 6.0 #11947
Missing fixed issues from Gradle 6.1 release notes #11954
Memory regression when resolving large artifacts while computing checksums #11966
Gradle 6.1 generates an empty .gradle and gradle directories on each execution in subproject directories #11971

We recommend that you use Gradle 6.1.1 over the initial release of Gradle 6.1.

Upgrade Instructions

Switch your build to use Gradle 6.1.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.1.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.1.x.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

`v6.1.0`

The Gradle team is excited to announce Gradle 6.1.

We would like to thank the following community contributors to this release of Gradle:
Mark Nordhoff,
Kazuki Matsuda,
Andrew Malyhin,
Emmanuel Guérin,
Nicholas Gates,
Bjørn Mølgård Vester,
Johnny Lim,
Benjamin Muskalla,
Ian Kerins,
Vladimir Sitnikov,
Michael Ernst,
Nelson Osacky,
Dmitriy Konopelkin,
and Steven Crockett.

Upgrade Instructions

Switch your build to use Gradle 6.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

`v6.0.1`

This is a patch release for Gradle 6.0.

This fixes several critical bugs in Gradle 6.0:

Incremental Java compilation is broken with Android 3.5.1 and Gradle 6.0 #11330
Unable to use a Provider as an artifact for the maven-publish plugin #11054
Implicit capabilities not always applied/detected #11300
maven-metadata.xml SHA256 and SHA512 checksums prevent publishing to Nexus #11308
Unable to properly resolve dynamic dependencies from mavenLocal() repo #11321
Kotlin DSL: fileTree(mapOf(...)) has unexpected behavior #11335
Attribute disambiguation rule for 'org.gradle.category' can cause unexpected type exception #11365

We recommend that you use Gradle 6.0.1 over the initial release of Gradle 6.0.

Upgrade Instructions

Switch your build to use Gradle 6.0.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=6.0.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v6.0.0`

The Gradle team is excited to announce a new major release, Gradle 6.0.

We would like to thank the following community contributors to this release of Gradle:
Nathan Strong,
Roberto Perez Alcolea,
Daniel Santiago,
Tetsuya Ikenaga,
Sebastian Schuberth,
Andrey Mischenko,
Shintaro Katafuchi,
Alex Saveau,
Mike Kobit,
Tom Eyckmans,
Artur Dryomov,
szhem,
Nigel Banks,
Sergey Shatunov,
Dan Sănduleac,
Vladimir Sitnikov,
Ross Goldberg,
jutoft,
Robin Verduijn,
Pedro Tôrres,
Michael Berry,
Evgeny Mandrikov,
lingocoder,
Robert Stupp,
and Predrag Knežević.

Upgrade Instructions

Switch your build to use Gradle 6.0 by updating your wrapper:

./gradlew wrapper --gradle-version=6.0

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.0.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

`v5.6.4`

This bug-fix release contains all changes from 5.6.1 through 5.6.3 as well as:

Can't configure kotlinOptions after upgrade to gradle 5.6.3 using kotlin-dsl #11083
Slow localhost look-up on macOS #11134

We recommend that you use Gradle 5.6.4 over any other 5.6.x release.

Upgrade Instructions

Switch your build to use Gradle 5.6.4 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.4

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.6.3`

This bug-fix release contains all changes from 5.6.1 and 5.6.2 as well as:

Let Kotlin DSL gracefully handle lambdas registered as extensions (5.6.3) #11014
Gradle Module Metadata compatibility for unique snapshots #11050
maven-publish publishes jars with wrong extension for known jar packagings like 'ejb' in 5.6 #10555
Regression in 5.5 when using dependency constraints for non-jar dependencies without a POM #10948
resolution failure when dependency locks and kotlin-dsl plugin are present #10697
Non-Kotlin extensions crash the build when using Kotlin DSL + Kotlin plugins #10729
Sporadic build failures with build-scan due to an overlapping ID assignment #10286
Prevent StackOverflowException caused by excessive 'or' via PatternMatcher #10330

We recommend that you use Gradle 5.6.3 over any other 5.6.x release.

Upgrade Instructions

Switch your build to use Gradle 5.6.3 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.3

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.6.2`

This bug-fix release contains changes to Gradle 5.6.1:

Duplicate entry in generated .classpath file in Gradle >= 5.6 (#10393)
Memory leak when using tasks that use Worker API and process isolation (#10411)

We recommend that you use Gradle 5.6.2 over 5.6.1.

Upgrade Instructions

Switch your build to use Gradle 5.6.2 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.2

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.6.1`

This bug-fix release contains changes to Gradle 5.6:

Unable to publish artifacts with custom classifier/extension from java project with Gradle 5.6 (#10287)
Regression in 5.6 signArchives (Duplicate key) (#10302)
Regression setting version for ArchiveTasks in 5.6 (#10311)
A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleKotlinCompilerWork (#10317)
DirectoryFileTree breaks SourceTask since 5.6 (#10322)
Regression: Unable to pass java.util.Properties object using Worker API in Gradle 5.6 (#10323)
Unable to publish multiple publications with same coordinates (#10333)
Gradle 5.6 - Resolving resources from buildSrc or plugins (#10347)

We recommend that you use Gradle 5.6.1 over 5.6.

Upgrade Instructions

Switch your build to use Gradle 5.6.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.6.0`

The Gradle team is excited to announce Gradle 5.6.

This release also contains an important security fix affecting some users.

This is the final minor release for Gradle 5.x. Read the release notes

We would like to thank the following community contributors to this release of Gradle:

Louis CAD,
Roberto Perez Alcolea,
Dan Sănduleac,
Andrew K.,
Noa Resare,
Juan Martín Sotuyo Dodero,
Semyon Levin,
wreulicke,
John Rodriguez,
mig4,
Evgeny Mandrikov,
Bjørn Mølgård Vester,
Simon Legner,
Sebastian Schuberth,
Ian Kerins,
Ivo Anjo,
Stefan M.,
Nickolay Chameev,
Dominik Giger,
Stephan Windmüller,
Zemian Deng,
Robin Verduijn,
Sandu Turcan,
Emmanuel Guérin,
Nikita Skvortsov,
and Christian Fränkel.

Upgrade Instructions

Switch your build to use Gradle 5.6 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6

Standalone downloads are available at gradle.org/releases.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.5.1`

This bug-fix release contains three changes to Gradle 5.5:

Combination of errorprone-gradle-plugin and options.fork = true causes Java compilation to fail in Gradle 5.5 #9897
Using dependency declaration gradleKotlinDsl() fails with 5.5 #9919
Chain of transitives aligned by same platform can lead to broken resolution #9882

We recommend that you use Gradle 5.5.1 over 5.5.

Upgrade Instructions

Switch your build to use Gradle 5.5.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.5.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.5.0`

The Gradle team is excited to announce Gradle 5.5.

Read the release notes

We would like to thank the following community contributors to this release of Gradle:
Martin d'Anjou,
Ben Asher,
Mike Kobit,
Erhard Pointl,
Sebastian Schuberth,
Evgeny Mandrikov,
Stefan M.,
Igor Melnichenko,
Björn Kautler,
Roberto Perez Alcolea and
Christian Fränkel.

Upgrade Instructions

Switch your build to use Gradle 5.5 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.5

Standalone downloads are available at gradle.org/releases.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.4.1`

This bug-fix release contains two changes to Gradle 5.4:

Fix inconsistent classpath ordering when dependencies have lots of excludes - #9197
Kotlin DSL IDEA script editor can't find JDK classes with Gradle 5.4 if Gradle JVM != Project SDK - #9195

We recommend that you use Gradle 5.4.1 over 5.4.

Upgrade Instructions

Switch your build to use Gradle 5.4.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.4.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.4.0`

The Gradle team is excited to announce Gradle 5.4.

Read the release notes

We would like to thank the following community contributors to this release of Gradle:
Ian Kerins,
Roberto Perez Alcolea,
Rodolfo Forte,
gla3dr,
and Stefan M..

Upgrade Instructions

Switch your build to use Gradle 5.4 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.4

Standalone downloads are available at gradle.org/releases.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.3.1`

This bug-fix release contains several changes to Gradle 5.3, notably:

Unable to use java-platform and maven-publish in multi-project: #8845
Unexpected exception when adding a plugin on buildSrc compile classpath: gradle/kotlin-dsl#1363

We recommend that you use Gradle 5.3.1 over 5.3.

Upgrade Instructions

Switch your build to use Gradle 5.3.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.3.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.3.0`

The Gradle team is excited to announce Gradle 5.3.

This release features support for publishing and consuming Gradle Module Metadata, feature variants or "optional dependencies", type-safe accessors in Kotlin precompiled script plugins, and more.

Read the Gradle 5.x upgrade guide to learn about breaking changes and considerations for upgrading from Gradle 5.0. If upgrading from Gradle 4.x, please read upgrading from Gradle 4.x to 5.0 first.

We would like to thank the following community contributors to this release of Gradle: Stefan M., Evgeny Mandrikov, Simon Legner, Raman Gupta, Florian Dreier, Kenzie Togami, Ricardo Pereira, Thad House, Joe Kutner, and Josh Soref.

Upgrade Instructions

Switch your build to use Gradle 5.3 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.3

Standalone downloads are available at gradle.org/releases.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.2.1`

This bug-fix release contains several changes to Gradle 5.2, notably:

Checkstyle issues with a single source file: #8394
BOM support conflicts: #8420

We recommend that you use Gradle 5.2.1 over 5.2.

Upgrade Instructions

Switch your build to use Gradle 5.2.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.2.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.2.0`

The Gradle team is excited to announce Gradle 5.2.

This release features a new Java Platform plugin, improved C++ plugins, new C++ project types for gradle init, service injection into plugins and project extensions, Kotlin DSL 1.1.3 and more.

Read the Gradle 5.x upgrade guide to learn about breaking changes and considerations for upgrading from Gradle 5.0. If upgrading from Gradle 4.x, please read upgrading from Gradle 4.x to 5.0 first. Users upgrading from 5.1 should not have to worry about breaking changes.

Upgrade Instructions

Switch your build to use Gradle 5.2 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.2

Standalone downloads are available at gradle.org/releases.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.1.1`

This bug-fix release contains several changes to Gradle 5.1, notably:

A daemon memory leak affecting all projects #8142
Incremental Java compilation #8194
A fix to Gradle's generated Javadoc in 5.1 #8183

We recommend that you use Gradle 5.1.1 over 5.1.

Upgrade Instructions

Switch your build to use Gradle 5.1.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.1.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v5.1.0`

The Gradle team is excited to announce Gradle 5.1.

This release features repository to dependency matching, production-ready configuration avoidance APIs, Gradle Kotlin DSL 1.1, and more.

Read the Gradle 5.x upgrade guide to learn about breaking changes and considerations for upgrading from Gradle 5.0.
If upgrading from Gradle 4.x, please read upgrading from Gradle 4.x to 5.0 first.

We would like to thank the following community contributors to this release of Gradle:
Mike Kobit,
Kent Fletcher,
Niklas Grebe,
Jonathan Leitschuh,
Sebastian Schuberth,
Dan Sănduleac,
Olivier Voortman,
Alex Saveau,
and Till Krullmann.

See the full set of release notes.

Upgrade Instructions

Switch your build to use Gradle 5.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.1

Standalone downloads are available at gradle.org/releases.

Reporting Problems

If you find a problem with Gradle 5.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle 5.1, and we look forward to your feedback via Twitter or on GitHub.

`v5.0.0`

The Gradle team is excited to announce Gradle 5.0.

This release features a production-ready Kotlin DSL, dependency version alignment (similar to and usable with Maven BOMs), task timeouts, Java 11 support, and more.

These release notes list what's new since Gradle 4.10. You can review the highlights since Gradle 4.0 here.

Read the Gradle 5.0 upgrade guide to learn about breaking changes and considerations for upgrading from Gradle 4.x.

We would like to thank the following community contributors to this release of Gradle: Jean-Baptiste Nizet, Jonathan Leitschuh, Ben McCann, Björn Kautler, Georg Friedrich, Stefan M., Xiang Li, Theodore Ni, James Justinic, Mike Kobit, Alex Saveau, Kevin Macksamie, Cliffred van Velzen, Artem Zinnatullin, Jakub Strzyżewski, Martin Dünkelmann, Thad House, Dan Sanduleac, Felipe Lima, and thc202.

Kotlin DSL 1.0

First and foremost, Gradle Kotlin DSL is now production-ready with it's 1.0 release! Authoring your build logic using Kotlin provides significant additional editing assistance in IDEs, including: improved completion, error highlighting, and refactoring tools. Please read our Gradle Kotlin DSL Primer and follow our migrating build logic from Groovy to Kotlin guide if you're interested. If you prefer the flexibility and dynamic features of Groovy, that's totally okay — the Groovy DSL will not be deprecated.

Dependency version alignment

This version of Gradle introduces dependency version alignment. This allows different modules belonging to the same logical group (platform) to have identical versions in a dependency graph. Maven BOMs can be imported to define platforms as well.

dependencies {
    // import a BOM. The versions used in this file will override any other version found in the graph
    implementation(enforcedPlatform("org.springframework.boot:spring-boot-dependencies:1.5.8.RELEASE"))
    
     // define dependencies without versions
    implementation("com.google.code.gson:gson")
    implementation("dom4j:dom4j")
    
     // this version will be overriden by the one found in the BOM
    implementation("org.codehaus.groovy:groovy:1.8.6")
}

More details about BOM import can be found in this section of the userguide.

Gradle build initialization features

gradle init functionality has been upgraded in this release: is now optionally interactive, includes new kotlin-library and kotlin-application project types, provides options for configuring project and package names, and more.

Searchable documentation

Search for Gradle Docs is back. The kind folks at Algolia kindly host an index used to allow you to search the user manual and DSL reference.

Gradle API Javadocs now take advantage of Javadoc built-in autocomplete, making it easier to find classes and methods you're interested in.

Task timeouts

You can now specify a timeout duration for a task, after which it will be interrupted. Read more about task timeouts in the docs.

HTTP retries during dependency resolution

When Gradle attempts to connect to a remote repository via HTTP, if it fails, Gradle will retry before blacklisting the repository.

No extra configuration is needed. See the section on HTTP retries for more information.

Performance features

Gradle can now be started as a low-prority process. This ensures that other applications like your IDE or browser stay responsive, even while a very demanding build is running.

When using @OutputFiles or @OutputDirectories with an Iterable type, Gradle used to disable caching for the task. This is no longer the case, and using such properties doesn't prevent the task from being cached. The only remaining reason to disable caching for the task is if the output contains file trees.

The JaCoCo plugin plugin now works seamlessly with the build cache. When applying the plugin with no extra configuration, the test task stays cacheable and parallel test execution can be used.

Java 11 runtime support

Java enthusiasts will be happy to read that this release supports running Gradle builds with JDK 11.

Plugin authoring features

This release introduces useful changes for plugin and custom task authors, including an API for creating SourceDirectorySets, improvements to the Provider API, and improved build cache compatibility.

Gradle Native features

The Gradle Native project continues to improve and evolve the native ecosystem support for Gradle.

Upgrade Instructions

Switch your build to use Gradle 5.0 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.0

Standalone downloads are available at gradle.org/release-candidate.

Reporting Problems

If you find a problem with Gradle 5.0, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle 5.0, and we look forward to your feedback via Twitter or on GitHub.

`v4.10.3`

This bug-fix release contains 3 changes to Gradle 4.10.2:

It also incorporates all fixes to 4.10.1 and 4.10.2.

We recommend that you use Gradle 4.10.3 over 4.10, 4.10.1 and 4.10.2.

Upgrade Instructions

Switch your build to use Gradle 4.10.3 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.3

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.3, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v4.10.2`

This bug-fix release contains 3 changes to Gradle 4.10.1:

Dependent module Scala compilation in test context fails for 4.10.1 #6735
Gradle fails to resolve project dependencies against Scala projects #6750
Candidate set provided to AttributeDisambiguationRule contains null entry #6747

We recommend that you use Gradle 4.10.2 over 4.10.1 or 4.10.

Upgrade Instructions

Switch your build to use Gradle 4.10.2 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.2

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.2, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v4.10.1`

This bug-fix release addresses 6 regressions in Gradle 4.10:

#6656: FileTreeElement.getPath() returns absolute system dependent filepath.
#6592: Up-to-date checks for missing files can be incorrect
#6612: Gradle fails when no incremental compile snapshot data available.
#6582: Gradle 4.10 incorrect ordering between dependencies of dependent tasks.
#6558: tasks.withType(ScalaCompile::class.java).configureEach fails on multi-project builds.
#6653: Double deprecation message when using publishing plugin.

In addition, the Gradle Kotlin DSL has been updated to 1.0 RC6, see the release notes for the list of included fixes.

Upgrade Instructions

Switch your build to use Gradle 4.10.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v4.10.0`

The Gradle team is pleased to announce Gradle 4.10. This is a big release.

First and foremost, this release of Gradle features an improved incremental Java compiler, now enabled by default.
This will result in significantly reduced Java compilation time in subsequent builds when outputs are not up-to-date or resolved from the build cache.

Chances are caches in those .gradle/ directories have accumulated a few (or a few dozen) gigabytes over time.
If so, you'll be relieved to know that Gradle will now periodically clean up unused /caches under GRADLE_USER_HOME and project root directories.

A moment you have anticipated is nearly here, as the Kotlin DSL reaches version 1.0 RC3.
Configuration avoidance, buildSrc refactoring propagation to the IDE, and lots of DSL polish make this the release to try.
Gradle Kotlin DSL 1.0 will ship with the next version of Gradle, 5.0.
Read this blog post for guidance on trying the Kotlin DSL and submitting feedback.

You can now use SNAPSHOT plugin versions with the plugins {} and pluginManagement {} blocks.
This is especially good news for Kotlin DSL users, who will get code assistance and auto-completion for these SNAPSHOT plugins.
Special thanks to Sébastien Deleuze for contributing.

Last but not least, included builds can now be nested.
This makes some common workflows more convenient, such as working on multiple source repositories at the same time to implement a cross-cutting feature.

We hope you will build happiness with Gradle 4.10, and we look forward to your feedback via Twitter or on GitHub.

Upgrade Instructions

Switch your build to use Gradle 4.10 quickly by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10

Standalone downloads are available at gradle.org/install.

`v4.9.0`

The Gradle team is pleased to announce Gradle 4.9.

First, publishing tools get some more love: projects that publish auxiliary publications (e.g. test fixtures) through maven-publish and ivy-publish can now be depended upon by other projects in the same build. There is also a new Publishing Overview chapter in the user manual and updates throughout the documentation regarding publishing artifacts using Maven and Ivy.

In addition to lazy tasks use, Kotlin DSL build scripts are evaluated faster with version 0.18.4, included in this version of Gradle. IntelliJ IDEA and Android Studio user experience is also improved.
See details in the Kotlin DSL v0.18.x release notes.

You can now pass arguments to JavaExec tasks directly from the command-line using --args:

❯ gradle run --args 'foo --bar'

No more need to hard-code arguments in your build scripts. Consult the documentation for the Application Plugin for more information.

Last but not least, this version of Gradle has an improved dependency insight report. Read the details further on.

We hope you will build happiness with Gradle 4.9, and we look forward to your feedback via Twitter or on GitHub.

Upgrade Instructions

Switch your build to use Gradle 4.9 quickly by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.9

Standalone downloads are available at gradle.org/install.

`v4.8.1`

This bug-fix release addresses 6 regressions in Gradle 4.8:

#5740: Maven Central dropped support for older TLS implementations. This makes the dependency resolution fail if the Gradle build runs on JDK 7.
#5701: Gradle 4.8 broke compatibility with the artifactory and bintray publishing plugins.
#5708: Gradle 4.8 sometimes fails with ConcurrentModificationException when project.tasks.withType() is used.
#5729: The dependency resolution engine sometimes fails with "Unexpected parent dependency" message, which became more apparent in Gradle 4.8.
#5722: Gradle 4.8 broke the ability of the SourceSet to override the compile tasks' destination directory.
#5692: Gradle 4.8 doesn't consider versions equal when using dependencySubstitution and failOnVersionConflict.

Upgrade Instructions

Switch your build to use Gradle 4.8.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.8.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.8.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v4.8.0`

The Gradle team is pleased to announce Gradle 4.8.

First and foremost, this release of Gradle features dependency locking: a mechanism for locking dependency versions which allows builds to become reproducible in the face of dynamic versions or version ranges.
Read the user manual chapter on dependency locking to learn how to take advantage of this exciting new feature.

The publishing plugins get some highly-anticipated improvements in this release:

The Signing Plugin now supports signing all artifacts of a publication.
The Maven Publish Plugin now provides a dedicated, type-safe DSL to customize the POM generated as part of a Maven publication.
The Ivy Publish Plugin now provides a dedicated, type-safe DSL to customize the Ivy module descriptor generated as part of an Ivy publication.
Configuration-wide dependency excludes are now published

The maven-publish and ivy-publish plugins are now considered stable and use of the maven plugin is discouraged as it will eventually be deprecated — please migrate.

User experience for incremental annotation processing is improved.
Compilation will no longer fail when a processor does something that Gradle detects will not work incrementally.
Unused non-incremental processors no longer prevent incremental compilation.
Finally, annotation processors are now able to decide dynamically if they are incremental or not.
This allows processors with extension mechanisms to check extensions for incrementality before enabling incremental annotation processing.

New native plugins continue to improve with better control over system include path for native compilation and other improvements.

Gradle 4.8 includes Kotlin DSL 0.17.5, bringing the latest Kotlin 1.2.41 release and many improvements to the user experience including location aware runtime error reporting, convenient configuration of nested extensions, faster and leaner configuration time, and TestKit support.
At the same time the IntelliJ IDEA Kotlin Plugin fixed many long standing build script editing related issues.
See details and examples in the Kotlin DSL v0.17 release notes.

We hope you build happiness with Gradle 4.8, and we look forward to your feedback via Twitter or on GitHub.

Upgrade instructions

Switch your build to use Gradle 4.8 quickly by updating your wrapper properties:

gradle wrapper --gradle-version=4.8

Standalone downloads are available at gradle.org/releases.

Reporting Problems

If you find a problem with Gradle 4.8, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v4.7.0`

The Gradle team is pleased to announce Gradle 4.7.

First and foremost, Gradle's incremental Java compiler can now run annotation processing incrementally. No user-facing configuration is necessary, but processor authors need to opt-in. We request annotation processor authors read the documentation for this feature and contact the Gradle team via the forum for assistance.

Java enthusiasts will be happy to read that this release supports running Gradle builds with JDK 10.

Gradle log output is now grouped by task for non-interactive executions, making interleaved logs a thing of the past on CI. It also enables build scan plugin v1.13 to show logs per task:

Moving on to other areas of user experience: running tests is further improved as failed tests now run first. Together with the --fail-fast option it provides the quickest possible feedback loop.

This release introduces an incubating new capability for Kotlin DSL users: precompiled script plugins. This means that you can create a Kotlin DSL script within a regular Kotlin source set and get the benefits of binary plugins. For example, src/main/kotlin/nyan.gradle.kts could be used as plugins { id("nyan") }.

Kotlin DSL v0.16 also includes Kotlin 1.2.31, a more consistent API, better IDE support, and more. See details and examples in the Kotlin DSL v0.16 release notes.

We hope you will build happiness with Gradle 4.7, and we look forward to your feedback via Twitter or on GitHub.

Upgrade Instructions

Switch your build to use Gradle 4.7 quickly by updating your wrapper properties:

gradle wrapper --gradle-version=4.7

Standalone downloads are available at gradle.org/releases.

Reporting Problems

If you find a problem with Gradle 4.7, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

`v4.6.0`