Skip to content

Commit

Permalink
Add link to maven performance comparison
Browse files Browse the repository at this point in the history
  • Loading branch information
eriwen committed Jun 14, 2017
1 parent fda8e5e commit 316546a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion subprojects/docs/src/docs/release/notes.md
Expand Up @@ -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.
Expand Down

0 comments on commit 316546a

Please sign in to comment.