# Cache Dependencies into Local Maven Repository from Gradle

**URL:** <https://discuss.gradle.org/t/cache-dependencies-into-local-maven-repository-from-gradle/7525>\
**Category:** Old Forum Archive\
**Created:** [November 8, 2011, 3:27pm UTC](https://discuss.gradle.org/t/cache-dependencies-into-local-maven-repository-from-gradle/7525 "2011-11-08T15:27:00Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![luke\_daley](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/luke_daley/32/9890_2.png) [@luke\_daley](https://discuss.gradle.org/u/luke_daley)\
**Post date:** [June 3, 2012, 9:56pm UTC](https://discuss.gradle.org/t/cache-dependencies-into-local-maven-repository-from-gradle/7525/15 "2012-06-03T21:56:00Z")

</div>

It would be too invasive on our part to write to another software system’s store without explicit instruction and use of a contract, which is what we do for our Maven plugin’s install task.

Also, the physical layout of Maven’s repository would not support the characteristics and features of our cache.

In summary, there are several reasons why using maven’s cache would be a bad thing for Gradle and one good reason (disk space optimization) and one debatable (state sync between the two tools). It’s just not going to happen.

---

_[View the full topic](https://discuss.gradle.org/t/cache-dependencies-into-local-maven-repository-from-gradle/7525)._