A build can only have a single settings.gradle file. Assuming settings.gradle is in the root directory and includes projects like so: include “P1:PP1” You can add a compile dependency like so: dependencies { compile(project(“:P1:PP1″)) } For more information, see the “Multi-Project Builds” chapter in the Gradle User Guide.
I found a better solution to be to exclude the functional tests from running on the command line or via the build file. For example, to run all tests except the functional tests, run: $ gradle check -x :functional-tests:check Then when building the project, you can let the subproject build but exclude their tests from … Read more
I was able to solve this problem in a relatively clean way. Improvements are certainly welcome! Although Gradle does not support multiple settings.gradle scripts out of the box, it is possible to create individual sub-projects each with their own settings.gradle file. Let’s say you have multi-project A that depends on multi-project B, each with their … Read more
Most of this is pretty normal to the http://www.gradle.org/docs/current/userguide/multi_project_builds.html page. However you are going to need to add evaluationDependsOn(‘:project1’) evaluationDependsOn(‘:project2’) so that gradle will evaluate project1 and project2 before module. In all the projects that contain code you will need to have an empty build.gradle file. This will also allow you to customize a project … Read more
The simplest way is to make MyProject a multi project with the Logger project as a subproject. settings.gradle in MyProject directory: include “:logger” project(“:logger”).projectDir = file(“../logger”) In the build.gradle of MyProject you can now reference this lib as a project: dependencies { compile ‘com.android.support:gridlayout-v7:18.0.0’ compile ‘com.android.support:appcompat-v7:18.0.0’ compile project(“:logger”) }
Deprecated – For Gradle 5.6 and above use this answer. In Project B, you just need to add a testCompile dependency: dependencies { … testCompile project(‘:A’).sourceSets.test.output } Tested with Gradle 1.7.