From 316546a5fcb4e2dfe1d6aa0b73a4e09e8cecb5a5 Mon Sep 17 00:00:00 2001 From: Eric Wendelin Date: Wed, 14 Jun 2017 07:42:23 -0700 Subject: [PATCH] Add link to maven performance comparison --- subprojects/docs/src/docs/release/notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/subprojects/docs/src/docs/release/notes.md b/subprojects/docs/src/docs/release/notes.md index 0fd3c9d69bcd..e843f543123e 100644 --- a/subprojects/docs/src/docs/release/notes.md +++ b/subprojects/docs/src/docs/release/notes.md @@ -2,7 +2,7 @@ The Gradle team is pleased to announce Gradle 4.0. We are excited to share some great new features and improvements with you in this release: -First and foremost, Gradle's [Build Cache](https://blog.gradle.org/introducing-gradle-build-cache) is now **production-ready for Java and Groovy** compilation and Java test tasks! This is further improved by overlapping outputs detection, configurable classpath normalization that avoids unnecessary task execution, and more listed in the [full release notes](#build-cache-improvements). The cacheability of other tasks, including other languages, will be completed in future releases. +First and foremost, Gradle's [Build Cache](https://blog.gradle.org/introducing-gradle-build-cache) is now **production-ready for Java and Groovy** compilation and Java test tasks! This provides remarkable performance, making Gradle builds [up to 100x faster than Maven](https://gradle.org/gradle-vs-maven-performance) in common scenarios. This is further improved by overlapping outputs detection, configurable classpath normalization that avoids unnecessary task execution, and more listed in the [full release notes](#build-cache-improvements). The cacheability of other tasks, including other languages, will be completed in future releases. We invite you to check out our new guide for [maximizing effectiveness of the Gradle Build Cache](https://guides.gradle.org/using-build-cache/). Now on to user experience: this release has a number of enhancements in logging and terminal display. Log output is now **grouped by project and task** when attached to a terminal — output from tasks run in parallel will no longer be interleaved. However, logging behaves the same as previous Gradle versions in non-interactive environments, and with `--console=plain`, to allow automated tools like CI systems to parse the logs they expect.