This message was deleted.

Probably because you use an ancient Gradle version. In recent versions a build without an explicit settings file is invalid. But if we turn back time to a Gradle version where it was valid. Gradle searches with a given algorithm for a settings script where the current directory could be a subproject of following some conventions. If it did find one, it checked whether the build is indeed a part of the build defined by that settings script. If it did not find the settings script of a build it is part in, Gradle assumed you are within a standalone single-project build. That it then tells it uses the

settings.gradle

in that directory is fine. Gradle will also tell you that it uses

build.gradle

files of projects that do not exist as long as they are defined in the settings script, because it is perfeclty fine if those files are absent as long as you are happy with the defaults. Same for the settings script. But even in the good old times where a settings script was not mandatory, each sane build should indeed have a settings script for at least two reasons: 1. to define the root project name instead of having it derived from the directory name 2. to save the time to search for another settings script that might included the current project

Thank you so much for the explanation. I learned something new today. For the record I'm using Gradle 6.8.3. I understand its fine to claim that but it's also a bit misleading on Gradle's part to say that upfront, considering that people use INFO level to know what's going on behind the scenes and such claims might confuse the end user at times.

Well, it is not really misleading. That is the file that is used. That it does not exist just means it is treated the same as it is were empty. But that is the file your would modify if you need to. And anyway as I said, in modern versions your wish was fulfilled, as a build without explicit assertions script is not valid anymore anyway. :-)