Execution failed for task ':configureChromeDriverBinary'. with gradle 8.7 #43
Comments
melix
added a commit
to micronaut-projects/micronaut-core
that referenced
this issue
Jul 17, 2024
JCenter is now redirecting to Maven Central, so it doesn't serve artifacts which were only in JCenter anymore. Of course, our build had such an artifact. It was brought through the "webdrivers" plugin, which depends on a grolifant version which is not on Maven Central. Unfortunately, upgrading that plugin is not straightforward. While there is an alternative, there is actually no version which is compatible with Gradle 8.7: erdi/webdriver-binaries-gradle-plugin#43 At the same time, the `test-geb` module was actually not tested on CI. The only way to run the tests was locally, and the instructions to do so were wrong, so it's unlikely that it gave any useful signal anywhere recently. As such, this commit removes the `test-suite-geb` module, at least until we have a proper replacement. Fixes #10988
melix
added a commit
to micronaut-projects/micronaut-core
that referenced
this issue
Jul 17, 2024
JCenter is now redirecting to Maven Central, so it doesn't serve artifacts which were only in JCenter anymore. Of course, our build had such an artifact. It was brought through the "webdrivers" plugin, which depends on a grolifant version which is not on Maven Central. Unfortunately, upgrading that plugin is not straightforward. While there is an alternative, there is actually no version which is compatible with Gradle 8.7: erdi/webdriver-binaries-gradle-plugin#43 At the same time, the `test-geb` module was actually not tested on CI. The only way to run the tests was locally, and the instructions to do so were wrong, so it's unlikely that it gave any useful signal anywhere recently. As such, this commit removes the `test-suite-geb` module, at least until we have a proper replacement. Fixes #10988
melix
added a commit
to micronaut-projects/micronaut-core
that referenced
this issue
Jul 17, 2024
JCenter is now redirecting to Maven Central, so it doesn't serve artifacts which were only in JCenter anymore. Of course, our build had such an artifact. It was brought through the "webdrivers" plugin, which depends on a grolifant version which is not on Maven Central. Unfortunately, upgrading that plugin is not straightforward. While there is an alternative, there is actually no version which is compatible with Gradle 8.7: erdi/webdriver-binaries-gradle-plugin#43 At the same time, the `test-geb` module was actually not tested on CI. The only way to run the tests was locally, and the instructions to do so were wrong, so it's unlikely that it gave any useful signal anywhere recently. As such, this commit removes the `test-suite-geb` module, at least until we have a proper replacement. Fixes #10988
graemerocher
pushed a commit
to micronaut-projects/micronaut-core
that referenced
this issue
Jul 22, 2024
JCenter is now redirecting to Maven Central, so it doesn't serve artifacts which were only in JCenter anymore. Of course, our build had such an artifact. It was brought through the "webdrivers" plugin, which depends on a grolifant version which is not on Maven Central. Unfortunately, upgrading that plugin is not straightforward. While there is an alternative, there is actually no version which is compatible with Gradle 8.7: erdi/webdriver-binaries-gradle-plugin#43 At the same time, the `test-geb` module was actually not tested on CI. The only way to run the tests was locally, and the instructions to do so were wrong, so it's unlikely that it gave any useful signal anywhere recently. As such, this commit removes the `test-suite-geb` module, at least until we have a proper replacement. Fixes #10988
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I tried to switch in my gradle projects which used webdriver-binaries-gradle-plugin to recent gradle 8.7 I started getting this error message when trying to build/tests those projects:
Execution failed for task ':configureChromeDriverBinary'while it worked just fine with the 8.6 version. I recreated the same outcome using geb-example-gradle as well.I'm using this java:
java version "11.0.19" 2023-04-18 LTSJava(TM) SE Runtime Environment 18.9 (build 11.0.19+10-LTS-225)Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.19+10-LTS-225, mixed mode)And here is a fullstacktrace from that geb-example-gradle project switched to gradle 8.7
gradle-plugin-error.txt
The text was updated successfully, but these errors were encountered: