# How to change multiproject dependency resolution behavior

**URL:** <https://discuss.gradle.org/t/how-to-change-multiproject-dependency-resolution-behavior/4030>\
**Category:** Old Forum Archive\
**Created:** [July 22, 2014, 3:19pm UTC](https://discuss.gradle.org/t/how-to-change-multiproject-dependency-resolution-behavior/4030 "2014-07-22T15:19:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason2](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@Jason2](https://discuss.gradle.org/u/Jason2)\
**Post date:** [July 22, 2014, 3:19pm UTC](https://discuss.gradle.org/t/how-to-change-multiproject-dependency-resolution-behavior/4030/1 "2014-07-22T15:19:00Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Peter\_Niederwieser](https://avatars.discourse-cdn.com/v4/letter/p/9f8e36/32.png) [@Peter\_Niederwieser](https://discuss.gradle.org/u/Peter_Niederwieser)\
**Post date:** [July 22, 2014, 3:37pm UTC](https://discuss.gradle.org/t/how-to-change-multiproject-dependency-resolution-behavior/4030/2 "2014-07-22T15:37:00Z")

</div>

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