Building a sub-project of a Gradle build, where another sub-project is Android

[mark_vieira]

I believe this is effectively the same question being asked here:

"Weak" dependencies in a multi-project setup

I have a simple multi-project setup. Project A is an Android client and Project B is a Tomcat-based backend that the Android client accesses. These two projects do not share any code. The Project A requires the Android plugin. Now here is the problem: when you cd into Project B (Tomcat) and run “gradle build”, gradle apparently includes Project A to compute the task graph (because it is referenced in settings.gradle). The unfortunate thing is that this requires a developer for Project B also to …