It would be really nice if gradle only resolved a dependency once per
build. If there is a new jar mid build I don't want to know about it!
It was also make things much faster.
- Peace
Dave
On Tue, May 31, 2011 at 12:27 PM, Szczepan Faber wrote:
> Hey,
>
> "-Divy.cache.ttl.default" is not a
Hey,
"-Divy.cache.ttl.default" is not a workaround for offline builds, e.g.
using this setting will not make gradle work in offline way.
It may be used as workaround for slow builds when version ranges are
used. At this moment, ivy version ranges with gradle make dependency
resolving slow because
I see that the gradle offline mode isn't supported yet. I also saw as
a work-around here using: http://issues.gradle.org/browse/GRADLE-320
gradle clean build -Divy.cache.ttl.default=eternal
gradle clean build -Divy.cache.ttl.default=1ms
Does this work around actually work?
If so would it be po
