Update dependency gradle to v3.5.1 #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/gradle-3.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.2.1->3.5.1Release Notes
gradle/gradle (gradle)
v3.5.1: 3.5.1Compare 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:
Upgrade Instructions
Switch your build to use Gradle 3.5.1 by updating your wrapper properties:
./gradlew wrapper --gradle-version=3.5.1Standalone 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: 3.5.0Compare 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.5Standalone 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: 3.4.1Compare 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:
Upgrade Instructions
Switch your build to use Gradle 3.4.1 by updating your wrapper properties:
./gradlew wrapper --gradle-version=3.4.1Standalone 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: 3.4Compare 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:
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-scanif 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.4Standalone 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: 3.3Compare Source
Gradle 3.3 is now available
This release of Gradle makes the
gradle tasksreport much faster for medium-to-large projects. By default,gradle taskswill now only display tasks which have been assigned a task group.For example, execution time was reduced from 554 seconds to 3 seconds on our perf-enterprise-large benchmark project — over 100x faster!
See the technical details on how and why this change was made in the full release notes.
It is now possible to compile native applications using Visual Studio 2015. Gradle will locate the Universal C Runtime required by the Visual C++ toolchain.
Kotlin build script support has further improved with significantly faster startup performance, increased API parity with Groovy-based build scripts, and better interoperability with Groovy plugins. See the gradle-script-kotlin v0.5.0 release notes for details.
Scala compilation startup time in large multi-project builds has been improved through enhancements to Gradle's integration with the Zinc Scala compiler. In earlier versions of Gradle, builds with many Scala projects could timeout and fail when building in parallel.
Tooling API generates more progress events. This means that IDEs will show a much clearer picture of what Gradle is doing during the configuration phase, resolving dependencies, and using composite builds. Details and pictures in the full release notes.
The Gradle GUI has been deprecated and will be removed in Gradle 4.0. An IDE which provides a UI for Gradle — IntelliJ IDEA, Eclipse, or NetBeans, for example, is recommended.
Check the full 3.3 release notes for more information.
Upgrade Instructions
Switch your build to use Gradle 3.3 quickly by updating your wrapper properties:
./gradlew wrapper --gradle-version=3.3Standalone downloads are available at https://gradle.org/gradle-download.
Reporting Problems
If you find a problem with Gradle 3.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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.