Gradle plugin: explicit dependency versions on Spring Boot Jackson 2 for plugin POM generation

[antoinelochet]

Hello,

When a project does not explicitely declare a dependency on "org.springframework.boot:spring-boot-jackson2", a error is triggered:

What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not find org.springframework.boot:spring-boot-jackson2:.
     Required by:
         buildscript of project ':app' > com.epages.restdocs-api-spec:com.epages.restdocs-api-spec.gradle.plugin:0.20.0 > com.epages:restdocs-api-spec-gradle-plugin:0.20.0 > com.epages:restdocs-api-spec-openapi-generator:0.20.0
         buildscript of project ':app' > com.epages.restdocs-api-spec:com.epages.restdocs-api-spec.gradle.plugin:0.20.0 > com.epages:restdocs-api-spec-gradle-plugin:0.20.0 > com.epages:restdocs-api-spec-openapi3-generator:0.20.0
         buildscript of project ':app' > com.epages.restdocs-api-spec:com.epages.restdocs-api-spec.gradle.plugin:0.20.0 > com.epages:restdocs-api-spec-gradle-plugin:0.20.0 > com.epages:restdocs-api-spec-postman-generator:0.20.0

I don't know why this issue did not happen when doing the development of #289, but this is the same issue with "org.springframework.boot:spring-boot-jackson2" than with all the Jackson3 dependencies that have been fixed in #292.

A workaround is to force the resolution on the dependency before the plugins block:

buildscript {
    configurations.all {
        resolutionStrategy {
            force("org.springframework.boot:spring-boot-jackson2:4.0.3")
        }
    }
}

[wodrobina]

A big thanks for reporting this issue and for proposing a temporary workaround.We will start looking into the issue soon. However, it may take some time before we are able to provide an official fix.

In the meantime, the workaround you suggested might help others encountering the same problem.