renovatebot(deps): update dependency gradle to v3.5.1

[mmoayyed]

This PR contains the following updates:

Package	Type	Update	Change
gradle (source)	gradle-wrapper	minor	3.0.0 -> 3.5.1

---

Release Notes

gradle/gradle

v3.5.1

Compare Source

This bug-fix release addresses an uncaught regression in v3.5.0. Consider upgrading to v4.0, which also contains the fix.

Fixed issue:

• gradle/gradle#​1811: mavenLocal broken when \ found in Maven settings.xml

Upgrade Instructions

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

./gradlew wrapper --gradle-version=3.5.1

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

Reporting Problems

If you find a problem with Gradle 3.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.

v3.5.0

Compare Source

Gradle 3.5 is now available

The Gradle team is pleased to announce Gradle 3.5.

First and foremost, we're excited to announce the new Build Cache! Beyond incremental builds, Gradle can save time by reusing outputs from previous executions of a task, resolving them locally or remotely. We’ve worked hard to ensure many built-in tasks are cacheable and safe to try; however, this feature should not be used in production without fully understanding its current limitations, so it is not enabled by default.

We have been testing this feature at scale for quite some time on the Gradle build itself and with enterprise partners, and the feedback has been very positive. While this feature is incubating, we are improving the user experience, documentation, and debuggability so that everyone can enable the Build Cache eventually.

We would like your feedback. Please read the Build Cache user manual, try it in non-critical environments, and submit GitHub issues with build scans if you encounter problems.

Next, we lamented that sometimes Gradle console output did not show all work-in-progress during a build (especially with --parallel), so we’ve developed brand new console output!

Gradle Script Kotlin v0.8.0 (included in the distribution) is a major step forward in
usability. It brings a more consistent DSL, convenient and type-safe access to contributed project extensions and conventions, much better error reporting, bug fixes and, of course, the latest and greatest Kotlin release.

Finally, plugin resolution rules give you tighter control over how plugins are resolved through the new pluginManagement {} block.

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

Check the full 3.5 release notes for more information.

Upgrade Instructions

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

./gradlew wrapper --gradle-version=3.5

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

Reporting Problems

If you find a problem with Gradle 3.5, 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.

v3.4.1

Compare Source

Gradle 3.4.1 is now available

This bug-fix release addresses uncaught regressions in v3.4.0 in the Java incremental compilation.

Fixed issues:

• gradle/gradle#​1474: Incremental compilation with literals in 3.4
• gradle/gradle#​1476: Compile avoidance should respect public constant changes

Upgrade Instructions

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

./gradlew wrapper --gradle-version=3.4.1

Standalone downloads are available at https://gradle.org/gradle-download.

Reporting Problems

If you find a problem with Gradle 3.4.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.

v3.4.0

Compare Source

Gradle 3.4 is now available

We're excited to bring you 3 incredible performance features in this release.

First up: Compile Avoidance. We've introduced a new mechanism for up-to-date checking of Java compilation that is sensitive to public API changes only. This means that if you change a comment or even a private API in a downstream project, Java compilation for upstream projects will be UP-TO-DATE.

Next: A stable incremental Java compiler. We've smartened the handling of constants, backed it with in-memory caches, and fixed many bugs. It is now production-ready for your build and has been promoted out of @Incubating.

Finally: A brand new Java Library Plugin. Use this when building a component intended to be used as a dependency from another project. It provides a strong separation between public (exported) and private code which not only gives great performance benefits (because consumers' compile classpaths are smaller), but also an architectural tool for library authors.

Put these together on our perf-enterprise-large benchmark Java project, and compilation time after a method body change is reduced from 2.5 minutes to 9 seconds! Let's put that in perspective:

It is not just large projects that reap the benefits, for example the same use case for Apache Polygene was reduced from 14 seconds to 7 seconds. Huge kudos to our performance team for delivering such massive performance improvements with this release.

You can learn more in this blog post about incremental compilation, compile avoidance and other performance features of Gradle 3.4.

Now, with your help and guidance we've been able to made a couple of highly-requested code-quality plugins improvements:

• The JaCoCo plugin now allows you to enforce code coverage metrics and fail the build if they're not met.
• The default version of JaCoCo used by the JaCoCo plugin has been raised and the plugin is now Java 9-ready.
• The Checkstyle plugin now allows a maximum number of warnings or errors to be configured.

A special thank you to those who voted and contributed to these issues.

The community's voice clearly indicated the need for verifying JaCoCo code coverage metrics. The JaCoCo plugin in Gradle 3.4 verifies code coverage metrics and will fail the build if code coverage falls below a configurable threshold. The plugin is also fully prepared to run on Java 9.

Last but not least, we've made it more convenient to let Gradle know when you want a build scan — just use --scan (or --no-scan if not). No need for the "magic" system property -Dscan.

We hope you're able to build happiness with Gradle 3.4, and we look forward to your feedback via Twitter or on GitHub and sharing other amazing features in 2017. Happy new year from the Gradle team!

Check the full 3.4 release notes for more information.

Upgrade Instructions

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

./gradlew wrapper --gradle-version=3.4

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

Reporting Problems

If you find a problem with Gradle 3.4, 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.

v3.3.0

Compare Source

v3.2.1

Compare Source

v3.2.0

Compare Source

v3.1.0

Compare Source

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[mmoayyed]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (3.5.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.