Closed holly-cummins closed 1 year ago
@holly-cummins This issue can probably be closed now, right?
In our project I just tested with the latest 4.4.0 version, but that resulted in an unholy mix of Groovy 3.0 (via Rest-Assured) and Groovy 4.0 (via Pact). I assume that Quarkus may also have other dependencies which rely on Groovy, otherwise it would be possible to upgrade to a newer Rest-Assured version, which also relies on Groovy 4.0.
You're right, @knutwannheden, Pact have fixed it upstream in https://github.com/pact-foundation/pact-jvm/issues/1615, and dependabot brought the fix in. There's just a comment in the code that needs tidying, so I'll do that and close this out. Thanks!
@holly-cummins What's your take on Pact 4.4.0 with Groovy 4.0? Have you encountered any issues with that?
@knutwannheden thanks for spotting the Pact 4.4.0 issues. I'll raise an issue to discuss, since at the moment they're not even passing the tests for this extension.
Upgrading Pact from 4.3.14 to 4.3.15 the tests no longer run and result in a failure with Antlr. The root cause is that Antlr changed their ATN format between 4.9.2 and 4.10, and Pact 4.3.15 brings in Antlr 4.11. This would be ok, except that Quarkus uses Antlr 4.9.2, and having the two versions of Antlr on the classpath causes ATN conflicts.
See https://github.com/pact-foundation/pact-jvm/issues/1615.
See also https://github.com/pact-foundation/pact-jvm/issues/1380, except in the other direction (Quarkus's pact is too old, rather than too new). I'm also looking at https://github.com/quarkusio/quarkus/pull/27298, which is a Quarkus PR to upgrade Quarkus's Antlr from 4.9.2 to a higher version. There's some discussion of Pact on that work item. I think the incompatible Antlr must be sneaking into the user test classpath from Quarkus.