Invalid Gradle build configuration when Spring Cloud Contract is included

As reported in spring-cloud/spring-cloud-contract gh-1795, the Gradle configuration as created by Initializer is invalid with respect to configuring the contracts extension. Presently, SpringCloudContractGradleBuildCustomizer.java#L75-L83, adds the configuration to a task with the name contracts which does not exist. This then results in build failures with the default project configuration directly provided by Initializer.

Incorrect:

tasks.named("contracts") {
    testFramework = org.springframework.cloud.contract.verifier.config.TestFramework.JUNIT5
}

Correct:

contracts {
    testFramework = org.springframework.cloud.contract.verifier.config.TestFramework.JUNIT5
}

Minimal reproducer: https://start.spring.io/#!type=gradle-project&language=java&platformVersion=2.7.0&packaging=jar&jvmVersion=17&groupId=com.example&artifactId=demo&name=demo&description=Demo project for Spring Boot&packageName=com.example.demo&dependencies=cloud-contract-verifier

[snicoll]

Yep, junit5 is the default. The error is to be expected. You need a contract.

[snicoll]

@bwgjoseph It doesn’t but we should be able to generate the right bits now. I’ll try to spare some cycles to look at it.