Fix deprecation warnings due to tasks calling getProject() at execution time

[wilkinsona]

Some of our custom tasks (org.springframework.boot.build.autoconfigure.AutoConfigurationMetadata is one) call getProject() at execution time. This results in a deprecation warning and means that our build will break with Gradle 9.0. While we won't be able to fix all such warnings in our build as some come from third-party plugins, we should update our own tasks.

[0x100]

Hi! As far as I understood, the build should not break with Gradle 8.0. The deprecated class there is org.gradle.api.internal.AbstractTask, its removal should not affect the getProject() method.

[wilkinsona]

The getProject() method isn't going away, but Gradle is going to prohibit/restrict calling it during task execution. That's what we want to address. To see the warnings you have to enable the STABLE_CONFIGURATION_CACHE feature preview.

[ThomazPassarelli]

Hi! I find this issue interesting. May I start working on it? Thanks in advance!

[wilkinsona]

Thanks for the offer, @ThomazPassarelli, but I've already made a start on this (several months ago now) and just need to find some time to finish it off.