1.) When we refresh the cache, do we plan also to consider the SHA1 values of the metadata files in the future? Right now we always download the metadata when we do a refresh. Not that I think this is a big issue. Just curious to understand the background and plans on this.
2.) The following looks like a bug to me. If you have a look at the cache-expiration example at: https://github.com/gradleware/live-demos/tree/master/cache-expiration - Publish the artifacts and call show on the consumer. - Publish again and call consumer:show with --refresh dependencies. Zoo is downloaded again (no sha1 file available). Moo is not downloaded again. It has a sha1 file but the sha1 file has changed. The moo metadata is downloaded again as part of the refresh. Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleware CEO, Gradleware - Gradle Training, Support, Consulting http://www.gradleware.com
