@Vampire W.r.t. https://gradle-community.slack.com/archives/CAHSN3LDN/p1790009935682299?thread_ts=1790005987.739679&cid=CAHSN3LDN I am pulling this into a separate conversation: I have noticed in the later Gradle 9 versions that if you have some task class that is statically compiled Groovy 3.x (plugin built under Gradle 8.x) and it uses a

onlyIf {}

within that class, it fails when configuration cache is active. I have not spent enough time investigating it, but the couple of times I saw it was enough to irritate me

No idea, never seen. But then, I would never write a published plugin in anything but pure Java and the lowest version the target minimum Gradle version supports as minimum unless some dependency requires a higher Java version anyway, most probably to prevent exactly such incompatibility issues. 🤷‍♂️ But maybe it is something to report and fix in the CC implementation?

I would report it IF I can craft up a simple enough reproducible case. (This means spending time to do it).

Shouldn't it be easy with

GradleTest

? 😄

I guess I had that coming