Closed tkrah closed 1 year ago
Do you please have idea how to fix it? Any PR to address this issue would be really appreciated 🙏
Unfortunately I am not familiar with the compose code here and have no time at the moment to understand the extension code to fix it - but maybe you can get some ideas from here:
https://github.com/gradle/gradle/issues/17446 https://github.com/spring-projects/spring-boot/pull/26903 https://github.com/spring-projects/spring-boot/commit/0f52bbc5607ad91fcd3fa2791b2130c5c0d4ee96
how to fix that. If I find time to have a closer look I'll provide a PR if possible.
The replacement docs also have this:
As a last resort, to apply some configuration represented by a Groovy Closure, a plugin can use {@link org.gradle.api.Project#configure(Object, Closure)}.
So maybe it's worth a try to use that.
@augi I tried it with that: https://github.com/avast/gradle-docker-compose-plugin/pull/413 - lets discuss stuff there.
It should be resolved in 0.17.1.
The whole extension (L316) and each "logical" compose declaration (L335) are emitting those warnings in Gradle 8.2.1+.
See: https://github.com/avast/gradle-docker-compose-plugin/blob/5c67f607ee23087398124f16c9e66d78f61602f1/src/main/groovy/com/avast/gradle/dockercompose/ComposeExtension.groovy#L4