This message was deleted.

But I'm using special custom sign plugin, which doesn't do signing itself, just provide setup and custom signing mechanism implementation for the default Gradle signing support. And this plugin using old Gradle version to build. And now how Gradle works internally. I would tell that if I running this plugin on 8.1.1 is should simply use all code from Gradle 8.1.1 and fact, that it is build with older Gradle should not be relevant not?

This isn’t a “fixed in Gradle” issue - somewhere in your build scripts (or that plugin) the configuration is referencing the project, which is not CC compatible.

So I will try also this plugin update to latest Gradle a try to build it myself.

to be clear - if a plugin is not CC compatible upgrading the Gradle version won’t help that. The plugin code needs to be adjusted.

Yes. if plugin definine some task in wrong way (not compatible with CC) it is obvious for me. But in the error was not a task from this custom plugin, but

org.gradle.plugins.signing.Sign

Which confusing me.

it could be in code that configures that plugin, either in your build script or another plugin.

And one more question. What if this custom plugin actually using one another X plugin which is not compatible But mine project also using this X plugin in the new version which is already compatible. Does it mean that Gradle will use only the latest version of X plugin. Or will load and use both of them?

To my knowledge the plugins go through dependency resolution which will, by default, pick the latest version. That may be problematic for the ‘other’ plugin if things are no longer compatible.

OK. I already found, that issue is really caused by custom plugin setuping signing, it doesn't declare any task, but extend

org.gradle.plugins.signing.signatory.SignatorySupport

class which is then used by Gradle itself inside of

org.gradle.plugins.signing.Sign

yes, looks like that AvastSigningExtension is the culprit.