This message was deleted.

That's not an error, just a warning. If you choose so, you can ignore it, especially as

buildSrc

is a reserved name and such special case anyway. But to get the warning away, you need to follow the advice. But following the advice makes sense anway, as each and every build should have a settings script and there set the root project name. Editing the build script does not help of course, you need to edit the settings script.

Well I don’t want caching to break. So I want to set the name. Is setting it to

buildSrc

correct?

Caching will not break in that case.

so it is an erroneous warning?

Yes and no. The warning is not wrong, you will just never do the action that causes the negative effect it wants to protect you from.

Thank you

I had gotten the same warning regarding an included build. I never did what the warning said, because I vaguely remember someone saying not to set a root project name for an included build because it causes some issues. Granted that memory is probably wrong, but I never got a chance to re-investigate.

Never heard of such problems. That would also be fatal, as the original intent of included build is too include builds that usually are stand-alone to test latest code version instead of released one.

Makes sense