|Tags||build-tool c c++ groovy java kotlin|
6.4.118 May 2020 04:31 minor feature: This is a patch release for Gradle 6.4. This fixes several critical bugs in Gradle 6.4: Regression: Different daemons are used between IDE and CLI builds for the same project #13069 Regression: Main-Class attribute always added to jar manifest when using application plugin #13057
6.405 May 2020 20:54 minor feature: The Gradle team is excited to announce Gradle 6.4. This release features highly anticipated support for building and testing Java Modules, precompiled Groovy DSL script plugins for better build logic organization, and a single lock file per project resulting in fewer lock files in projects using dependency locking.
6.325 Mar 2020 14:45 major bugfix: The Gradle team is excited to announce Gradle 6.3.
6.2.205 Mar 2020 08:41 major bugfix: 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.
6.2.125 Feb 2020 09:48 minor bugfix: 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 All issues fixed We recommend that you use Gradle 6.2.1 over the initial release of Gradle 6.2.
6.217 Feb 2020 12:20 major feature: The Gradle team is excited to announce Gradle 6.2. This release adds built-in dependency checksum and signature verification, provides a shareable read-only dependency cache and emits helpful documentation links when you have deprecations in your build.
6.1.127 Jan 2020 18:33 major feature: 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 All issues fixed We recommend that you use Gradle 6.1.1 over the initial release of Gradle 6.1. Read the full release notes
6.008 Nov 2019 19:42 major feature: The Gradle team is excited to announce a new major version of Gradle, 6.0. A major highlight of this release is the vastly improved feature set in dependency management. Some of the features were released in stages, but with Gradle 6.0 they are stable and production ready. We publish Gradle Module Metadata by default, which makes these new features available between projects and binary dependencies. In the JVM ecosystem, we've made incremental Java and Groovy compilation faster, added support for JDK13 and provided out of the box support for javadoc and source jars. For Scala projects, we've updated the Zinc compiler and made it easier to select which version of Zinc to use. For Gradle plugin authors, we've added new APIs to make it easier to lazily connect tasks and properties together, made useful services available to worker API actions and Gradle will complain at runtime if a task appears misconfigured. In the native ecosystem, we've added support for Visual Studio 2019 and the latest C++ standards. This release contains some updates to help protect the integrity and security of your build. As always, we also incorporated some smaller changes and many other fixed issues.
5.6.318 Oct 2019 14:30 minor bugfix: 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.
5.6.206 Sep 2019 18:37 minor bugfix: 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.
5.6.128 Aug 2019 09:03 minor bugfix: 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 - RuntimeException: Unable to load FastStringService (#10347) We recommend that you use Gradle 5.6.1 over 5.6.
5.615 Aug 2019 12:28 minor bugfix: The Gradle team is excited to announce Gradle 5.6. This release also contains an important security fix affecting some users: https://github.com/gradle/gradle/security/advisories/GHSA-4cwg-f7qc-6r95 This is the final minor release for Gradle 5.x. Read the release notes: https://docs.gradle.org/5.6/release-notes.html
5.5.111 Jul 2019 13:56 minor bugfix: 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.
5.501 Jul 2019 07:04 minor bugfix: This release features improvements to build init to generate plugin projects, an API for transforming dependency artifacts, the ability to declare organization-wide Gradle properties, lots of new native plugin documentation and more.
5.4.125 May 2019 08:07 minor bugfix: 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.
5.3.101 Apr 2019 07:39 major feature: 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.
5.2.126 Feb 2019 09:59 major feature: 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.
5.1.111 Jan 2019 13:36 major feature: 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.
5.001 Dec 2018 20:52 major feature: 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.
4.10.219 Sep 2018 20:12 minor bugfix: 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.
4.10.115 Sep 2018 18:28 major feature: 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.
4.1001 Sep 2018 20:29 major feature: 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.
4.903 Aug 2018 06:39 major feature: #5772 - Build operations for task registration/creation are emitted by default #5771 - Gradle 4.8+ fails with NotSerializableException on Intellij IDEA project import #5750 - Default "**/*.java" include filter added to Java compilation tasks in Gradle 4.8 #5724 - Gradle Includes Vulnerable XercesImpl Jar. Upgrade when patched version available on Maven Central. #5714 - Do not compile or execute a build script when there is a failure building the build script classpath #5646 - Creating a task inside configureEach causes CME #5638 - Remove @Incubating annotations from publishing types #5583 - Project configuration build operations are no longer nested #5565 - Enable injection of RepositoryResourceAccessor in ComponentMetadataRule #5541 - Reduce memory used in FileUtils#calculateRoots #5526 - Add caching support to ComponentMetadataRule #5505 - gradle distribution depends on jackson-databind version 2.8.11 which has insecure deserialization vulnerability (CVE-2018-5968) #5473 - Allow an included build to use file collection dependencies #5379 - Broken link in docs despite looking correct in adoc #5311 - Introduce Publishing chapter in User Guide #5305 - TestWorker fails to catch SecurityException when calling System.setSecurityManager #5278 - ClassCastException when generating Eclipse files for Gradle #5207 - Why do javadoc tasks of depending projects depend on each other? #5091 - Removing project .gradle directory disproportionately degrades buildSrc performance #4960 - Recompile instead of failing when annotation processors violate the incremental contract #4895 - Included build failure does not break the build #4506 - Gradle Test Kit functional tests fail in an unrecoverable way #4370 - Composite build failures are reported incorrectly for dependency on different subprojects of an included build #3490 - A failure in an included build should be reported at the end of logging output #1743 - The application plugin's "ru
ManageYou can also help out here by:
← Update project
or flagging this entry for moderator attention.