add gradle 8.7 compatibility via org.ysb33r.gradle:grolifant-herd:4.0.0

[jamesfredley]

will resolve:

• Execution failed for task ':configureChromeDriverBinary'. with gradle 8.7 #43
• Grails 7: Gradle 8.7+: JCenter retirement breaks webdriver-binaries-gradle-plugin and/or grolifant grails/grails-testing-support#443

replaces:

• gradle 8.7+ compatibility jamesfredley/webdriver-binaries-gradle-plugin#1

Changes were made to enable tests to run on Windows 11.

Fully tested against:

• https://github.com/grails/grails-functional-tests
• https://github.com/grails/grails-testing-support - also requires org.asciidoctor:asciidoctor-gradle-jvm from 4.0.1 to 4.0.3

[jamesfredley]

@erdi @jonnybot0

[jonnybot0]

Hey, @jamesfredley! Neither I nor the Geb project maintain this repository. For our part, we're actively working to move from this to Selenium Manager, which solves the same core problem. You can see the in-progress pull request for this at apache/groovy-geb#200.

Even without that update to Geb, you can start using Selenium Manager by upgrading to Selenium 4.11 or later. It works just fine with the latest Geb release. I would recommend upgrading to the latest version of Selenium you can in your environment, as Selenium Manager did have a few bugs in the earlier iterations that are now resolved. That may entail Java updates, though, depending on your project.

Obviously, you can always use an artifact built from your fork here in the interim, and if @erdi wants to merge this here, more power to you both. :)

[jamesfredley]

Thanks for the reply.

For Grails, we are moving the default Geb setup to use org.testcontainers:selenium via https://github.com/grails/geb/blob/7a50d0aa78671f41ce0237b98b501cf844208081/src/testFixtures/groovy/grails/plugin/geb/ContainerGebSpec.groovy#L49 which is working great.

This PR would help users that want to use Gradle 8.6+ with webdriver-binaries-gradle-plugin.