On 24/12/2010, at 2:36 AM, Ken Avery wrote:
> Hello,
>
> Due to issues we have had with dependencies being downloaded multiple times
> during a build cycle, we are looking for a way to only run the dependency
> download process. Basically, we want the ability to prime the gradle cache
> before running the actual project build. We do have several external
> dependencies plus many internal project dependencies. It would only be the
> external dependencies that we care about. Has anyone done this or have any
> suggestions on how to achieve this?
>
You can iterate over the files of a configuration to trigger a download:
task resolve << {
configurations.compile.each { }
}
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
