search

jansauer / gradle-print-coverage-plugin

Scraps jacoco test reports and prints the code coverage to the console
16 stars 9 forks source link

Update dependency gradle to v4.10.3 #9

Closed jansauer closed 5 years ago

jansauer commented 5 years ago

This PR contains the following updates:

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

Release Notes

gradle/gradle ### [`v4.10.3`](https://renovatebot.com/gh/gradle/gradle/releases/v4.10.3) [Compare Source](https://renovatebot.com/gh/gradle/gradle/compare/v4.10.2...v4.10.3) This bug-fix release contains **3** changes to Gradle 4.10.2: - [#​7510](https://renovatebot.com/gh/gradle/gradle/pull/7510) - [#​6849](https://renovatebot.com/gh/gradle/gradle/issues/6849) - [#​7014](https://renovatebot.com/gh/gradle/gradle/issues/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 . #### Reporting Problems If you find a problem with Gradle 4.10.3, please file a bug on [GitHub Issues](https://renovatebot.com/gh/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v4.10.2`](https://renovatebot.com/gh/gradle/gradle/releases/v4.10.2) [Compare Source](https://renovatebot.com/gh/gradle/gradle/compare/v4.10.1...v4.10.2) 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](https://renovatebot.com/gh/gradle/gradle/issues/6735) - Gradle fails to resolve project dependencies against Scala projects [#​6750](https://renovatebot.com/gh/gradle/gradle/issues/6750) - Candidate set provided to `AttributeDisambiguationRule` contains null entry [#​6747](https://renovatebot.com/gh/gradle/gradle/issues/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 . #### Reporting Problems If you find a problem with Gradle 4.10.2, please file a bug on [GitHub Issues](https://renovatebot.com/gh/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v4.10.1`](https://renovatebot.com/gh/gradle/gradle/releases/v4.10.1) [Compare Source](https://renovatebot.com/gh/gradle/gradle/compare/v4.10.0...v4.10.1) This bug-fix release addresses **6** regressions in Gradle 4.10: - [#​6656](https://renovatebot.com/gh/gradle/gradle/issues/6656): FileTreeElement.getPath() returns absolute system dependent filepath. - [#​6592](https://renovatebot.com/gh/gradle/gradle/issues/6592): Up-to-date checks for missing files can be incorrect - [#​6612](https://renovatebot.com/gh/gradle/gradle/issues/6612): Gradle fails when no incremental compile snapshot data available. - [#​6582](https://renovatebot.com/gh/gradle/gradle/issues/6582): Gradle 4.10 incorrect ordering between dependencies of dependent tasks. - [#​6558](https://renovatebot.com/gh/gradle/gradle/issues/6558): `tasks.withType(ScalaCompile::class.java).configureEach` fails on multi-project builds. - [#​6653](https://renovatebot.com/gh/gradle/gradle/issues/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](https://renovatebot.com/gh/gradle/kotlin-dsl/releases/tag/v1.0-RC6) 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 . #### Reporting Problems If you find a problem with Gradle 4.10.1, please file a bug on [GitHub Issues](https://renovatebot.com/gh/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v4.10.0`](https://renovatebot.com/gh/gradle/gradle/releases/v4.10.0) [Compare Source](https://renovatebot.com/gh/gradle/gradle/compare/v4.9.0...v4.10.0) 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](https://docs.gradle.org/4.10/release-notes.html#incremental-java-compilation-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`](https://docs.gradle.org/4.10/release-notes.html#periodic-cache-cleanup) 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](https://renovatebot.com/gh/gradle/kotlin-dsl/releases/tag/v1.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](https://blog.gradle.org/gradle-kotlin-dsl-release-candidate) for guidance on trying the Kotlin DSL and submitting feedback. You can now use [SNAPSHOT plugin versions with the `plugins {}`](https://docs.gradle.org/4.10/release-notes.html#use-snapshot-plugin-versions-with-the-plugins-{}-block) 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](https://renovatebot.com/gh/sdeleuze) for contributing. Last but not least, [included builds can now be nested](https://docs.gradle.org/4.10/release-notes.html#nested-included-builds). 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](https://twitter.com/gradle) or [on GitHub](https://renovatebot.com/gh/gradle/gradle). #### 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](https://gradle.org/install/). ### [`v4.9.0`](https://renovatebot.com/gh/gradle/gradle/releases/v4.9.0) [Compare Source](https://renovatebot.com/gh/gradle/gradle/compare/v4.8.1...v4.9.0) 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](https://renovatebot.com/gh/gradle/gradle/issues/1061) in the same build. There is also a [new Publishing Overview chapter](https://docs.gradle.org/4.9/userguide/publishing_overview.html) 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](https://renovatebot.com/gh/gradle/kotlin-dsl/releases/tag/v0.18.4). You can now pass arguments to `JavaExec` tasks [directly from the command-line](https://docs.gradle.org/4.9/release-notes.html#command-line-args-supported-by-javaexec) 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](https://docs.gradle.org/4.9/userguide/application_plugin.html#sec:application_usage) for more information. Last but not least, this version of Gradle has an _improved dependency insight report_. Read the [details further on](https://docs.gradle.org/4.9/release-notes.html#improved-dependency-insight-report). We hope you will build happiness with Gradle 4.9, and we look forward to your feedback [via Twitter](https://twitter.com/gradle) or [on GitHub](https://renovatebot.com/gh/gradle). #### 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](https://gradle.org/install). ### [`v4.8.1`](https://renovatebot.com/gh/gradle/gradle/releases/v4.8.1) [Compare Source](https://renovatebot.com/gh/gradle/gradle/compare/v4.8.0...v4.8.1) This bug-fix release addresses **6** regressions in Gradle 4.8: - [#​5740](https://renovatebot.com/gh/gradle/gradle/issues/5740): Maven Central dropped support for older TLS implementations. This makes the dependency resolution fail if the Gradle build runs on JDK 7. - [#​5701](https://renovatebot.com/gh/gradle/gradle/pull/5701): Gradle 4.8 broke compatibility with the `artifactory` and `bintray` publishing plugins. - [#​5708](https://renovatebot.com/gh/gradle/gradle/issues/5708): Gradle 4.8 sometimes fails with `ConcurrentModificationException` when `project.tasks.withType()` is used. - [#​5729](https://renovatebot.com/gh/gradle/gradle/pull/5729): The dependency resolution engine sometimes fails with "Unexpected parent dependency" message, which became more apparent in Gradle 4.8. - [#​5722](https://renovatebot.com/gh/gradle/gradle/issues/5722): Gradle 4.8 broke the ability of the `SourceSet` to override the compile tasks' destination directory. - [#​5692](https://renovatebot.com/gh/gradle/gradle/issues/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 . #### Reporting Problems If you find a problem with Gradle 4.8.1, please file a bug on [GitHub Issues](https://renovatebot.com/gh/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v4.8.0`](https://renovatebot.com/gh/gradle/gradle/releases/v4.8.0) [Compare Source](https://renovatebot.com/gh/gradle/gradle/compare/v4.7.0...v4.8.0) The Gradle team is pleased to announce Gradle 4.8. First and foremost, this release of Gradle features [dependency locking](https://docs.gradle.org/4.8/release-notes#locking-of-dynamic-dependencies): 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](https://docs.gradle.org/4.8/userguide/dependency_locking.html) 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](https://docs.gradle.org/4.8/release-notes#signing-publications). - The Maven Publish Plugin now provides a dedicated, type-safe [DSL to customize the POM generated](https://docs.gradle.org/4.8/release-notes#customizing-the-generated-pom) as part of a Maven publication. - The Ivy Publish Plugin now provides a dedicated, type-safe [DSL to customize the Ivy module descriptor generated](https://docs.gradle.org/4.8/release-notes#customizing-the-generated-ivy-module-descriptor) as part of an Ivy publication. - Configuration-wide [dependency excludes are now published](https://docs.gradle.org/4.8/release-notes#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](https://docs.gradle.org/4.8/release-notes#improved-incremental-annotation-processing). 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](https://docs.gradle.org/4.8/release-notes#better-control-over-system-include-path-for-native-compilation) for native compilation and [other improvements](https://renovatebot.com/gh/gradle/gradle-native/blob/master/docs/RELEASE-NOTES.md#changes-included-in-gradle-48). 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](https://renovatebot.com/gh/gradle/kotlin-dsl/releases/tag/v0.17.5). We hope you build happiness with Gradle 4.8, and we look forward to your feedback [via Twitter](https://twitter.com/gradle) or [on GitHub](https://renovatebot.com/gh/gradle). #### 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](https://gradle.org/releases). #### Reporting Problems If you find a problem with Gradle 4.8, please file a bug on [GitHub Issues](https://renovatebot.com/gh/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss).

Renovate configuration

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

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

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

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

This PR has been generated by Renovate Bot.