Ok. Clarified. Thanks for your reply.
Below is the problem I am trying to resolve.
In our company we have many project hierarchies
There are many such hierarchies …
i.e., same core modules will be part of many client projects. But, the
rootProject for each client project is different. So, I am in a position to have
settings.gradle in each module. No harm in that.
But, the problem comes when we add a core module with some dependencies. We are to add that module in lot of overlay
To handle such scenarios, I am having one common
WrapperRootProject. The build.gradle of
WrapperRootProject will add the actual root project (
project-d in case of Client-1) as dependency.
WrapperRootProject in which I have
paths.txt file to list the paths of all the modules. In
WrapperRootProject, I have to include only the projects that are dependencies of the actual root project (
Some programming logics, I am writing in
WrapperRootProject/settings.gradle to infer the DAG hiearachy of the
Is it the best way to solve this scenario?