There's, in impression, one metadata cache according to repository, yet Gradle keeps only one artifact cache for all dependencies. Binary artifacts are kept via the SHA-1 hash code in their contents, now not the repo they got here from or their group:artifact:version metadata. hence, all the metadata caches percentage universal entry to an area, disk-based shop of downloaded binary artifacts. within the earlier instance, an inner Artifactory repo can have a replica of commons-codec:commons-codec:1. 6, and Maven significant can have an analogous. in the event that they are either legitimately serving an identical JAR—as outlined through either documents sharing a similar SHA-1 hash code—then Gradle will in basic terms obtain the binary artifact as soon as, and shop it in a single position on disk. Gradle is predicated seriously on hashes to optimize obtain functionality; whilst resolving a dependency, it is going to first try to obtain the much-smaller SHA from the repo, skipping the obtain if it determines that it already has that content material within the artifact cache. There are a number of vital command line switches that influence the way in which Gradle makes use of its dependency cache. The --offline change tells Gradle to exploit cached dependencies, and never to try to re-resolve whatever (e. g. , altering dependencies) opposed to networked repositories. this is often necessary whilst operating with no community connection or whilst a wanted repository is offline. The --refresh-dependencies swap, in contrast, forces Gradle to visit the community to re-examine and re-fetch all dependency metadata. it is going to no longer obtain redundant modules if an artifact with the matching SHA-1 is already found in the artifact cache. this is important to make sure that you're development opposed to the very most modern of any altering or dynamic dependencies. Configuring answer procedure each dependency configuration has a solution method linked to it. In such a lot builds, this technique operates backstage and out of the view of construct masters and builders alike, yet dependency difficulties can come up that require its customization. at this time, there are 3 components of the method for you to swap: what to do whilst a model clash arises, even if to strength models of yes artifacts, and what caching semantics to use to altering and dynamic dependencies. Let’s examine those in flip. Failing on model clash considering that Gradle resolves dependencies transitively, independently declared dependencies can result in conflicting types of a few module they either rely on. for instance, an internet shape processing API may possibly depend upon commons-collections:commons-collections:3. 2. 1, while an older vendor-specific company integration module could depend on commons-collections:commons-collections:2. 1. Gradle will realize that diversified types of an analogous module are within the dependency graph, and by way of default it is going to opt for the more recent model. although, construction the firm integration module with Commons Collections three. 2. 1 will possibly not paintings. you need to find out about the clash and fail the construct. you are able to do this, both globally or on a per-configuration foundation, as in Example 4-31.