This message was deleted.

yes, dependencies should be automatically substituted

thanks for your reply, currently I have two main problems, these modules are shipped as libraries so I have a

com.android.library

plugin in their

build.gradle

file, however when I try to sync the project including that module in the build using

includeBuild()

I get the following exception:

* Exception is:
org.gradle.api.plugins.UnknownPluginException: Plugin [id: 'com.android.library'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Included Builds (None of the included builds contain this plugin)
- Plugin Repositories (plugin dependency must include a version number for this source)

the second bullet doesn't really makes sense to me since the plugin is indeed part of the included build, but I'm not sure about the other two. Is this a common issue that I can resolve somehow?

I would first try to make sure that the build works without any substitution

already tried that, but the result is the same

I suspect that your build is simply not working and it has nothing to do with dependency substitution

yes that's already declared in the project's

build.gradle.kts

file

there should not be an issue there

is there something additional that the module's

build.gradle

file should have? I'm using some custom Gradle scripts using

apply from: "/script_path"

but I don't see how that could be an issue

True composite builds must be fully independent builds