chore(deps): update dependency gradle to v4.10.3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	References
gradle	gradle-wrapper	minor	4.4.0 -> 4.10.3	homepage, source

---

Release Notes

gradle/gradle

v4.10.3

Compare Source

This bug-fix release contains 3 changes to Gradle 4.10.2:

• #​7510
• #​6849
• #​7014

It also incorporates all fixes to 4.10.1 and 4.10.2.

We recommend that you use Gradle 4.10.3 over 4.10, 4.10.1 and 4.10.2.

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.10.3

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

Reporting Problems

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

v4.10.2

Compare Source

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.

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.10.2

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

Reporting Problems

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

v4.10.1

Compare Source

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.

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.10.1

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

Reporting Problems

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

v4.10.0

Compare Source

The Gradle team is pleased to announce Gradle 4.10. This is a big release.

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.

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

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.10

Standalone downloads are available at gradle.org/install.

v4.9.0

Compare Source

The Gradle team is pleased to announce Gradle 4.9.

First, publishing tools get some more love: projects that publish auxiliary publications (e.g. test fixtures) through maven-publish and ivy-publish can now be depended upon by other projects in the same build. There is also a new Publishing Overview chapter in the user manual and updates throughout the documentation regarding publishing artifacts using Maven and Ivy.

In addition to lazy tasks use, Kotlin DSL build scripts are evaluated faster with version 0.18.4, included in this version of Gradle. IntelliJ IDEA and Android Studio user experience is also improved.
See details in the Kotlin DSL v0.18.x release notes.

You can now pass arguments to JavaExec tasks directly from the command-line using --args:

❯ gradle run --args 'foo --bar'

No more need to hard-code arguments in your build scripts. Consult the documentation for the Application Plugin for more information.

Last but not least, this version of Gradle has an improved dependency insight report. Read the details further on.

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

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.9

Standalone downloads are available at gradle.org/install.

v4.8.1

Compare Source

This bug-fix release addresses 6 regressions in Gradle 4.8:

• #​5740: Maven Central dropped support for older TLS implementations. This makes the dependency resolution fail if the Gradle build runs on JDK 7.
• #​5701: Gradle 4.8 broke compatibility with the artifactory and bintray publishing plugins.
• #​5708: Gradle 4.8 sometimes fails with ConcurrentModificationException when project.tasks.withType() is used.
• #​5729: The dependency resolution engine sometimes fails with "Unexpected parent dependency" message, which became more apparent in Gradle 4.8.
• #​5722: Gradle 4.8 broke the ability of the SourceSet to override the compile tasks' destination directory.
• #​5692: Gradle 4.8 doesn't consider versions equal when using dependencySubstitution and failOnVersionConflict.

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.8.1

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

Reporting Problems

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

v4.8.0

Compare Source

The Gradle team is pleased to announce Gradle 4.8.

First and foremost, this release of Gradle features dependency locking: a mechanism for locking dependency versions which allows builds to become reproducible in the face of dynamic versions or version ranges.
Read the user manual chapter on dependency locking to learn how to take advantage of this exciting new feature.

The publishing plugins get some highly-anticipated improvements in this release:

• The Signing Plugin now supports signing all artifacts of a publication.
• The Maven Publish Plugin now provides a dedicated, type-safe DSL to customize the POM generated as part of a Maven publication.
• The Ivy Publish Plugin now provides a dedicated, type-safe DSL to customize the Ivy module descriptor generated as part of an Ivy publication.
• Configuration-wide dependency excludes are now published

The maven-publish and ivy-publish plugins are now considered stable and use of the maven plugin is discouraged as it will eventually be deprecated — please migrate.

User experience for incremental annotation processing is improved.
Compilation will no longer fail when a processor does something that Gradle detects will not work incrementally.
Unused non-incremental processors no longer prevent incremental compilation.
Finally, annotation processors are now able to decide dynamically if they are incremental or not.
This allows processors with extension mechanisms to check extensions for incrementality before enabling incremental annotation processing.

New native plugins continue to improve with better control over system include path for native compilation and other improvements.

Gradle 4.8 includes Kotlin DSL 0.17.5, bringing the latest Kotlin 1.2.41 release and many improvements to the user experience including location aware runtime error reporting, convenient configuration of nested extensions, faster and leaner configuration time, and TestKit support.
At the same time the IntelliJ IDEA Kotlin Plugin fixed many long standing build script editing related issues.
See details and examples in the Kotlin DSL v0.17 release notes.

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

Upgrade instructions

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

gradle wrapper --gradle-version=4.8

Standalone downloads are available at gradle.org/releases.

Reporting Problems

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

v4.7.0

Compare Source

The Gradle team is pleased to announce Gradle 4.7.

First and foremost, Gradle's incremental Java compiler can now run annotation processing incrementally. No user-facing configuration is necessary, but processor authors need to opt-in. We request annotation processor authors read the documentation for this feature and contact the Gradle team via the forum for assistance.

Java enthusiasts will be happy to read that this release supports running Gradle builds with JDK 10.

Gradle log output is now grouped by task for non-interactive executions, making interleaved logs a thing of the past on CI. It also enables build scan plugin v1.13 to show logs per task:

Moving on to other areas of user experience: running tests is further improved as failed tests now run first. Together with the --fail-fast option it provides the quickest possible feedback loop.

This release introduces an incubating new capability for Kotlin DSL users: precompiled script plugins. This means that you can create a Kotlin DSL script within a regular Kotlin source set and get the benefits of binary plugins. For example, src/main/kotlin/nyan.gradle.kts could be used as plugins { id("nyan") }.

Kotlin DSL v0.16 also includes Kotlin 1.2.31, a more consistent API, better IDE support, and more. See details and examples in the Kotlin DSL v0.16 release notes.

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

Upgrade Instructions

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

gradle wrapper --gradle-version=4.7

Standalone downloads are available at gradle.org/releases.

Reporting Problems

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

v4.6.0

Compare Source

The Gradle team is pleased to announce Gradle 4.6.

First and foremost, this release of Gradle includes built-in support for JUnit Platform and the JUnit Jupiter/Vintage Engine, also known as JUnit 5 support.
You can use the new filtering and engines functionality in JUnit 5 using the examples provided below and in the documentation.

Thank you to the JUnit team for helping to achieve JUnit Platform support, and a special thank you to Andrew Oberstar for extraordinary contributions toward this effort.

Also regarding testing, you can now improve your testing feedback loop when running JVM-based tests using the new fail-fast option for Test tasks, which stops the build immediately after the first test failure.

// Example JUnit 5 and fail-fast test configuration
test {
    useJUnitPlatform {
        excludeTags 'slow'
        includeEngines 'junit-jupiter', 'junit-vintage'
    }

    failFast = true
}

Moving on to dependency management improvements: you can now declare dependency constraints for transitive dependencies and avoid problems caused by oft-hidden upstream dependency changes.

This release also features enhanced Maven dependency compatibility: support for importing BOMs, optional dependencies, and compile/runtime separation when consuming POMs.
For now you must enable these features by adding enableFeaturePreview('IMPROVED_POM_SUPPORT') to your settings.gradle file, as they break backward compatibility in some cases.

This version of Gradle also comes with a couple especially useful new APIs for task development. You can now declare custom command-line flags for your custom tasks, for example: gradle myCustomTask --myfoo=bar. In addition, tasks that extend Test, JavaExec or Exec can declare rich arguments for invoking the underlying executable. This allows for better modeling of tools like annotation processors.

Speaking of annotation processors, it is now more convenient to declare dependencies that are annotation processors through the new annotationProcessor dependency configuration. Using a separate dependency configuration for annotation processors is a best practice for improving performance.

Kotlin DSL v0.15.6 is included in this release of Gradle, and features initialization scripts support, nicer script compilation error reporting, performance improvements, and better IntelliJ IDEA integration. Details are available in the linked release notes.

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

Upgrade Instructions

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

gradle wrapper --gradle-version=4.6

Standalone downloads are available at gradle.org/releases.

Reporting Problems

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

v4.5.1

Compare Source

This bug-fix release addresses 3 regressions in Gradle 4.5.

Changes in dependency management caused a regression in 4.5 where in some rare cases a dependency could be imported into a different scope than the one declared.

Starting in 4.5, the build cache configuration is shared between builds part of a composite build. NullPointerException could be observed if the parent build finished before the different composites. This lifecycle issue has now been resolved.

A regression in Eclipse project generation caused a sub-project to be added as a dependency to itself, resulting in an error when opening the project in Eclipse.

For the full list of fixed issues, see the 4.5.1 GitHub milestone.

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.5.1

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

Reporting Problems

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

v4.5.0

Compare Source

The Gradle team is pleased to announce Gradle 4.5.

First and foremost, this release of Gradle features improvements to the build cache:

• Caching for C and C++ compilation is now stable.
• The ANTLR plugin now takes advantage of the build cache.
• A couple of rough edges to build cache behavior have been polished, read more in the detailed release notes.

In addition to cacheability improvements for native development, incremental compilation for C/C++ does finer-grained analysis of dependencies between source files and header files, which will result in fewer files compiled and a higher cache hit-rate. Read details about C and C++ compilation improvements here.

Now on to performance improvements everyone can enjoy: less memory consumption and faster up-to-date behavior. Gradle 4.5 features much more memory-efficient incremental compilation. Combined with less file canonicalization, faster task selection, and faster variant-aware dependency resolution, this results in up to 30% faster up-to-date checking. The improvement will be especially pronounced for projects with a large number of constants, as is typical in Android projects. For example, here are 2 snapshots comparing cross-build caches.

The 1st one from Gradle 4.4 using 440MB:

This 2nd snapshot from Gradle 4.5 using 280MB:

---

Next up, you can finally sign artifacts using gnupg-agent. Special thanks to Christoph Böhme for contributing this highly-anticipated feature.

Documentation has been upgraded in this release, with use-case oriented examples for several highly trafficked pages, improved navigation, and a more pleasant experience in many ways. Read details about the improvements, or just start with the new docs home page.

Individual deprecation warnings are no longer displayed in console output by default, as many users often cannot take action on deprecation warnings from third party plugins. You can now control the verbosity of logging deprecation warnings.

Last but not least, 2 Kotlin DSL updates:

• You can now generate Gradle Kotlin DSL scripts using gradle init --dsl kotlin.
• Kotlin DSL v0.14 is included in this release of Gradle. It features code navigation to Gradle sources in IDEs with the Gradle binary distribution (not just -all anymore), embedded Kotlin upgraded to 1.2.0 and more.

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

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.5

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

Reporting Problems

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

v4.4.1

Compare Source

This bug-fix release addresses 3 regressions in Gradle 4.4.

We started shipping JGit 4.5.3.2017081-r in Gradle 4.4. Some of the non-shaded JGit resources leaked into the gradleApi() dependency and caused problems in some builds. We now shade all of JGit's resources.

Some builds using Kotlin DSL had problems applying the build-scan plugin in Gradle 4.4. We've updated to kotlin-dsl 0.13.2.

Gradle 4.4 contained changes to internal APIs that broke the popular Nebula dependency lock plugin. This release restores binary compatibility for that plugin. Internal APIs are subject to change, although we try to be mindful of the impact of every change in each Gradle release. If particular internal APIs are useful, please open an issue describing your use case, so we can judge where our public APIs are lacking.

For the full list of fixed issues, see the 4.4.1 GitHub milestone.

Upgrade Instructions

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

./gradlew wrapper --gradle-version=4.4.1

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

Reporting Problems

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

---

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. View repository job log here.