On Sun, Jan 23, 2011 at 10:18 AM, Mathias Kalb <mathias.k...@prodato.de>wrote:
> Hi Hans, > > as Peter pointed out, the version matchers (dynamic revisions) are the >> "problem". What Ivy allows though, is to define a time to live (ttl) for >> dynamic revisions. Unfortunately we don't expose this configuration option >> yet but of course we should do and will do so soon. Again, filing an issue >> would be appreciated. >> > What should the issue contain? The "define a time to live (ttl) for dynamic > revisions"? Yes. Thanks Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleorg CEO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz > > > > >> One more thing in regard to the performance. Even without dynamic >> revisions, Ivy's retrieving of dependencies is probably the biggest chunk of >> the incremental build. I'm talking about the situation when all dependencies >> are in the local cache. The JFrog guys have written a complete new >> implementation of an Ivy cache manager (they call it the wharf). This new >> manager has many advantages (no wrong error messages, concurrency, ...). We >> also hope that it will speed things up. The first impression is that it >> does. We want to integrate it in 1.0-M1 which is scheduled for February. >> >> >> That sounds very good. > > regards, > Mathias Kalb > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
