This message was deleted.

I think you should stray from using

Task.project

as much as possible

agreed, just trying to determine what my situation is currently 🙂

using

Task.getProject()

or any instance of

Project

is a problem because of Configuration Cache https://docs.gradle.org/8.1.1/userguide/configuration_cache.html#config_cache:requirements:use_project_during_execution Config cache tries to store the Gradle config to disk using Java Serialization, but it can’t store a Project because it’s too big and complicated. But if you’re only running tasks that aren’t loaded from the config cache, then you’re not going to have a problem. But maybe those warnings were coming from Gradle plugins that were updated in 8.1.1 to be Config Cache compatible, or maybe you updated some other plugins as well that also fixed Config Cache problems?

ok but again, that doesn't address my question

if your build is running okay then there’s no problem 👍 But yes, the “don’t use Project” restriction still applies.

again, I'm skeptical that it's "running ok" because this was a warning in 7.6 that it would cause deprecation failure and that didn't seem to happen...because there's a disconnect I'm looking for some verification from the gradle community about whether or not this deprecation failure should have happened or not

https://docs.gradle.org/current/userguide/upgrading_version_7.html#task_project

Calling Task.getProject() from a task action at execution time is now deprecated and will be made an error in Gradle 8.0. This method can be used during configuration time, but it is recommended to avoid doing this.

no, you're repeating part of my question

what sort of clarification are you looking for? I’m not sure what else can answer your question more than a link to the docs

I stated what I'm trying to get for clarification...if you can only link me to the docs, then kindly wait for someone else to answer

do you know what the causes were for the warnings you saw?

Did you enable the

STABLE_CONFIGURATION_CACHE

feature preview when on 7.6 and removed this during the upgrade to 8.1.1?

yes, it's enabled in gradle.settings but set to false in our gradle.properties

Actually if

STABLE_CONFIGURATION_CACHE

is still enabled, you should still get the depreaction warning even if you disabled the configuration cache.

interesting ok...I might want to just remove it to be safe then until I can rewrite the plugins responsible for that pesky task.project stuff