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

Gradle Community

no, the specific blocks `buildscript`, `pluginManagement`, and `plugins` are extracted and executed independently. it would be a chicken-and-egg problem otherwise

I think it could maybe work if you put it to the parent projects class path.

hmm. in principle that seems logical, but in practice that doesn't work, Gradle doesn't use the parent classpath when evaluating these blocks

What a pity. Good that I placed all the conditionals then. :-D

Would a janky way of doing it be to extend that plugin (from the repo I'm trying to add) in my build-logic and then just reference that plugin instead in my module? Or perhaps some variation of that.

Although I suppose thats not that helpful, because I guess i'd be using buildSrc in the composite-build to now define a method to setup the repo

The question is, why you actually want to use a `buildscript` block at all. If you think about adding one, that's more a sign that either your build script contains logic that should better be moved to a custom task is custom plugin, which then has the needed dependency, or that you use legacy way to apply a plugin.