This message was deleted.

No. It’s a special, magical subproject. buildSrc only works off the root project.

That's probably good, there are no "turtles all the way down" issues I could introduce

You can use an included build instead. Included builds can include other builds. 🙂

More precisely: buildSrc is not like a “subproject” - but like a separate Gradle “build” (with a bit of magic, yes 🙂 ) Yes you can (and should) do this with included builds as @Vampire suggests. And there are use cases for it. I wouldn’t just neglect the idea of doing it because of possible turtles. 😉 Here for example, I use a separate ‘build’ called ‘settings’ that defines a Settings Plugin which I then use in the ‘main’ build as well as in the ‘plugins’ build (which effectively is buildSrc as included build) https://github.com/jjohannes/gradle-project-setup-howto/tree/main/gradle/settings (separate build, like buildSrc of buildSrc) https://github.com/jjohannes/gradle-project-setup-howto/blob/main/gradle/plugins/settings.gradle.kts (Used in “buildSrc”) https://github.com/jjohannes/gradle-project-setup-howto/blob/main/settings.gradle.kts (used in “main” build)

And btw. the answer of @Chris Lee was actually wrong.

buildSrc

can have its own

buildSrc

, I just tried it as I meant to remember it is possible. Whether it makes sense is a different topic. 😄

Ah thanks for trying. I was wondering about it… I also wasn’t sure anymore. 🙂