Hello, We are running a CI build of some of our Gradle applications. These builds are run inside Docker containers in an ‘empty’ system. To improve build times, we cache the dependencies of the Gradle home folder (the wrapper and caches directories). Summarized, the build is split up into many mod…

The dependency verification feature of Gradle does something like that internally, when calling --write-verification-metadata. Note, however, that as the documentation explains, it’s an approximation of what dependencies could be downloaded during a build. In particular, if a task uses what we call…

Hello, I have solved a similar use case. The following script provides a task that can leverage the incremental task support of Gradle, without resolving configurations for other tasks (thanks to the task configuration avoidance api ). allprojects { tasks.register("downloadDependencies", Copy)…

Thank you both for the answers. This helped me and the results look promising! @CedricChampeau It seems that dependency verification is only added in Gradle 6? I could not find that documentation for version 5.

Force resolving (and downloading) all dependencies

Help/Discuss

CedricChampeau (Cédric Champeau) May 15, 2020, 7:45am 5

Dependency verification was introduced in Gradle 6.2: https://docs.gradle.org/6.2/release-notes.html#dependency-verification

Topic		Replies	Views
Download dependencies task Help/Discuss	0	1172	January 4, 2019
Do not download dependencies for all configurations Help/Discuss	3	3616	July 14, 2015
Pre-downloading dependencies Help/Discuss	2	864	August 28, 2017
Gradle resolves dependencies too early in lifecycle ... how to prevent and catch this behavior Old Forum Archive	5	4541	April 4, 2014
Download all dependencies Old Forum Archive	4	4557	May 19, 2014

Force resolving (and downloading) all dependencies

Related topics