Subprojects and multiple settings.gradle scripts

[JamesWald]

Continuing the discussion from Is there any alternative to using settings.gradle for multi project builds?:

@luke_daley

One issue is that every *.gradle file in the current directory and above would have to be searched for the “settings” block which would be very costly.

Another is that “looking” for the settings block is complicated, because we couldn’t just execute the scripts as certain build script functions can’t be performed until the whole build structure is mapped. Also, this would in itself have a performance penalty compared to a special purpose file.

I was able to workaround the one settings.gradle limitation by applying subproject settings.gradle scripts with a projectDir update. This scheme supports multiple layers and doesn’t require redundant configuration. Details here: build automation - Multiple settings gradle files for multiple projects building - Stack Overflow