From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Why don't you just publish both?
Usually if you split code to separate projects, I recommend to also publish them separately.

My goal is to have full control over a toolchain (this includes usage of a custom resolver) used in all published projects. And I found no way how to apply the toolchain with the resolver to the project with the resolver itself. So this is the only reason why I do it the way I described. 

Release one version without that control, then apply the last released version in the build?

Much like the Java compiler being written in Java. Initial version had to be in since other language.

I would lie if I said that I didn't think about that solution. In our company I have to make every single Gargle/build related stuff with "for dummies" phrase in my mind.
Even if your solution sounds right, it involves additional steps to be executed every time the implementation changes. My experience tells me, that this is no-go for this very situation. 

Even though I wouldn't do it, you can use a dynamic version, so that always the latest version is used. But you have to be very careful with backwards compatibility then.