# How do I always use the latest version of a changing module

**URL:** <https://discuss.gradle.org/t/how-do-i-always-use-the-latest-version-of-a-changing-module/5314>\
**Category:** Old Forum Archive\
**Created:** [November 10, 2011, 10:05am UTC](https://discuss.gradle.org/t/how-do-i-always-use-the-latest-version-of-a-changing-module/5314 "2011-11-10T10:05:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![daz](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/daz/32/2475_2.png) [@daz](https://discuss.gradle.org/u/daz)\
**Post date:** [November 10, 2011, 3:12pm UTC](https://discuss.gradle.org/t/how-do-i-always-use-the-latest-version-of-a-changing-module/5314/2 "2011-11-10T15:12:00Z")

</div>

By default, Gradle treats a module version (eg “myorg:myproj:1.0”) as unchanging over time, allowing us to cache the module meta-data and artifacts indefinitely. If you have a module version that has content (meta-data or artifacts) that can change over time, you can mark the module as ‘changing’.

```gradle
dependencies {
    compile group: "group", name: "projectA", version: "1.1", changing: true
}

```

Normally, Gradle will still cache changing modules for a 24 hour period. You can configure this cache timeout using something like:

```gradle
configurations.all {
    resolutionStrategy.cacheChangingModulesFor 0, 'seconds'
}

```

You can read more about dynamic versions and changing modules [here](http://gradle.org/releases/latest/docs/userguide/dependency_management.html#sub:dynamic_versions_and_changing_modules).

---

_[View the full topic](https://discuss.gradle.org/t/how-do-i-always-use-the-latest-version-of-a-changing-module/5314)._