This message was deleted.

Why do you want to?

buildSrc

is not a subproject, but a completely separate "standalone" build that just happens to be executed before your main build and added to its parent classloader. In most cases you should probably not do what you try to, thus I'm asking for your original intent.

Our custom plugin contains other plugin version determination, but it`s version in project where we applying our custom plugin setted up in buildSrc

The way to handle this is to have the plugins defined in

buildSrc

be applied and make that information available through an extension.

How can this information be applied through the extension? We can do something with dsl and use an extension method that will intercept the version we specify, but this is not the version that will be resolve, due to version conflicts. Perhaps there is a normal way to understand the version of the plugin?

--scan

gives information about the plugin version, so it's possible?

I guess you can query the resolved state of the buildscript configurations and generate some resources file from that, which you can then expose as extension. But what do you need this information for in the main build?