Gradle plugin fail on gradle version 8.6 about spring-cloud-contract HOT 8 CLOSED

we encountered pretty much the same problem using spring-cloud-contract-gradle-plugin:4.1.1

from spring-cloud-contract.

Yes, 4.1.1 for us too.

from spring-cloud-contract.

@shanman190 please help 🙏

from spring-cloud-contract.

@marcingrzejszczak, yeah I'll take a look. Just initial review of the Gradle proper jvm-test-suite plugin shows that the API surface that we use is the same, but they renamed the return type from DependencyAdder to DependencyCollector. However, we don't use the type directly, but rather indirectly, so we shouldn't have been broken here.

To summarize, I'm not sure why it's saying the method isn't found and we should be compatible with Gradle 8.6 without any changes. I'll try to debug it here soon and see what's going on.

from spring-cloud-contract.

@welovelain, what version of the Spring Cloud Contract Gradle Plugin are you using?

from spring-cloud-contract.

The Gradle team upstream has chosen to leave the API as is, so I'll submit a PR to use reflection to handle the 7.6-8.5 version ranges.

from spring-cloud-contract.

I have same issue with version 4.0.3.

from spring-cloud-contract.

So I've reviewed this and it is a binary breaking change at the JVM level. The code compiles correctly on 8.5 and 8.6. but using a plugin version built with 8.6 on a lower Gradle version results in the same issue as well.

from spring-cloud-contract.