This message was deleted.

I had asked myself the same in the past. Whenever Gradle docs talk about subprojects, they seem to only refer to one level below the root project.

They work just fine. Although when you

include(":foo3:bar1")

it implicitly declare

include(":foo3")

.

The "conventional name" is still "multi-project build". There is no distinctinction and nothing special about how deep the project tree is nested.

I heard them called nested projects, nested subprojects or just projects/subprojects since they're not any different then when you use flat directory structure.

Sorry if this gets slightly off-topics, but I also have wondered (but never tested) whether both the

root

and

foo3

projects could have

settings.gradle

files that each only include their direct dependencies, but then still from the root directory you could refer to

:foo3:bar1

. That would be very convenient, but I guess it does not work...

A settings script is for a build, not for a project If you want it like that, you have to make

foo3

an included build

settings.gradle[.kts]

is only for root of the build but you could compose them using

includeBuild