martin-ober commented on issue #288: URL: https://github.com/apache/groovy-geb/issues/288#issuecomment-3705367271
> Hey, [@martin-ober](https://github.com/martin-ober) - apologies that I've been quiet on your question. The past few weeks I've been a bit slammed from various quarters (work and home). Being unable to promise a timeline, I didn't respond. > > Having dug into this reasonably deeply today, I'm beginning to think that the better course is to revert the PR that originally introduced the bug. I've opened a PR for that here ([#299](https://github.com/apache/groovy-geb/pull/299)). I'm going to seek a review from [@Vampire](https://github.com/Vampire) , as he's got as much context on this as me. > > If you're in a jam, and can't wait for the release train (which I can't make timeline promises on just now), my best suggestion would be to build your own internal release candidate from that branch and use that to upgrade your pipelines in the interim. That should restore the original behavior of the `clearCacheAndQuitDriver` method, but should otherwise have all the Geb 8 updates you're needing. Otherwise, keep an eye on the Groovy mailing list, this repo, or the Geb website for the next release. > > Thanks for your patience and interest in Geb. Hi @jonnybot0 Thank you for your feedback and thank you for your commitment to the project. I hope you didn't take my inquiry as a complaint, because that was not my intention. English is not my native language, so it may sound a little awkward. I found a workaround to kill the process myself and only clean the caches in the factory. This allowed me to get my pipelines running for the current geb and selenium versions. Once the bug is fixed in geb, I can switch back to the “proper” implementation. Thank you for taking care of this issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
