diff options
| author | Daniel Lacasse <lacasseio@users.noreply.github.com> | 2021-08-26 11:40:02 -0700 |
|---|---|---|
| committer | Google Java Core Libraries <java-libraries-firehose+copybara@google.com> | 2021-08-26 11:40:51 -0700 |
| commit | 97537a324571558d9c91bb4b669e6acbbbc439ff (patch) | |
| tree | 9df7e94e2855a14880211e5c5c79383ec872b431 | |
| parent | 874777b7c08e01f59793e4eaaeaac1739541e19f (diff) | |
| download | auto-97537a324571558d9c91bb4b669e6acbbbc439ff.tar.gz | |
Upgrade Gradle Test Kit to 7.2
It isn't exactly necessary to upgrade Gradle Test Kit to the latest
version as Gradle Test Kit as with normal Java dependencies. The Gradle
Test Kit JARs contains plumbing used to execute a Gradle build within as
part of testing scenarios. The JARs are usually generated by the Gradle
distribution at runtime. As the classes are released with each new
Gradle version, they may not change between versions. The
`dev.gradleplugins` project rerelease the Gradle Test Kit JARs to be used outside of a Gradle build and with a different Gradle
version. Unfortunately, we keep the Gradle distribution versioning
which leads to confusion about the "latest" version. Generally,
using the latest version is safe but keep in mind the Gradle Test Kit
JARs depend on the Gradle API, Groovy and Kotlin. If your project has a
strong opinion on the version of those dependencies, you will need to
resolve the version conflict. Note that Groovy and Kotlin dependencies
are mostly for the DSL part of Gradle, which is unlikely to leak in Test
Kit but could via the implementation of the classes.
See https://github.com/gradle-plugins/toolbox/issues/51 and https://github.com/gradle-plugins/gradle-api/commit/34cb7f38429b7980e9c0c4396971df4fb42dcf8b
Only the new version (7.2) for [Gradle API](https://repo1.maven.org/maven2/dev/gradleplugins/gradle-api/7.2/gradle-api-7.2.pom) and [Gradle Test Kit](https://repo1.maven.org/maven2/dev/gradleplugins/gradle-test-kit/7.2/gradle-test-kit-7.2.pom) has the fix for the POM.xml. If older versions are required, we can re-release an updated version. Don't hesitate to open additional issues regarding POM.xml issues, users usually use Gradle to resolve the dependencies, your feedback is very useful.
Fixes #1160
COPYBARA_INTEGRATE_REVIEW=https://github.com/google/auto/pull/1160 from lacasseio:lacasseio/upgrade-test-kit-to-7.2 6435cd04b77436cb0de11b1c5b34e4f637bc3592
PiperOrigin-RevId: 393171389
| -rw-r--r-- | value/src/it/functional/pom.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/value/src/it/functional/pom.xml b/value/src/it/functional/pom.xml index eaaac4a2..3dafa4b5 100644 --- a/value/src/it/functional/pom.xml +++ b/value/src/it/functional/pom.xml @@ -93,7 +93,7 @@ <dependency> <groupId>dev.gradleplugins</groupId> <artifactId>gradle-test-kit</artifactId> - <version>6.8.3</version> + <version>7.2</version> <scope>test</scope> </dependency> <dependency> |