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 <[email protected]> wrote: > 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 you'll have extra remote calls with each build > regardless of your local cache. > > I updated the ticket so that it's clearer :) > Cheers! > Szczepan > > On Mon, May 30, 2011 at 12:15 PM, phil swenson <[email protected]> wrote: >> 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 possible to write an offline task that sets >> -Divy.cache.ttl.default=1ms >> >> so you could run "gradle offline build" and it would perform a >> System.setPropert("ivy.cache.ttl.default", "1ms") ??? >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > > -- > Szczepan Faber > Principal engineer@gradleware > Lead@mockito > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
