How to change multiproject dependency resolution behavior

(mezlight) #1

I currently have a multi-project setup and I only want to build one project but when I build the project gradle tries to resolve the dependencies of all subprojects. Is there a way to ignore/skip this dependency check? None of the projects depend on each other. In the future, we are going to convert an ant & ivy build environment with 20 modules/projects (over 50 developers) to a gradle multi-project and I wouldn’t want the build fail because of a dependency of a project I don’t care about.

(Peter Niederwieser) #2

Gradle resolves dependencies just-in-time when they are first accessed. Perhaps something is wrong with the build (scripts).