This message was deleted.

In the specific case of

buildSrc

it indeed is a bit misleading, yes. But you should always have a settings script anyways and having the root project name defined shouldn't hurt either 🙂

well for the conventional

buildSrc

having a settings.gradle is often totally redundant

I wonder that it actually still works as at some point it was made an error to have a build without settings script. But I guess

buildSrc

also there has an exception rule as too many builds would have been broken by that.

I understand the point of having a

settings.gradle

file, I'm really commenting about the specific

buildSrc

case. This error was reported by a colleague of mine, and I think it's misleading.

And if I would use

buildSrc

(I usually use inluded builds for build logic), I would probably have a settings script anyway to define repositories, maybe include the version catalog of the parent build, ...

I know. And using included builds has quite a few issues (I still cannot use a composite build for multiple Micronaut projects because of many bugs or limitations of composites)

Oh, really? 😞 Didn't hit any problems I remember since quite some time. I'm curious, what issues do you have?

https://github.com/gradle/gradle/issues/23633 for example