G'day Currently, we are caching changing modules for 24 hours by default. This means that even though we know the module may change, we only check for updated version once per day.
I think this confuses users, who expect changing modules (SNAPSHOTs) to be up-to-date. I'm guessing that maven works this way? *I propose we make 0 seconds the default cache timeout for changing modules*(user configurable). When we do a check, we follow this process for the meta-data file as well as any artifacts: 1) Attempt to download an SHA1 key for the artifact 2) If the downloaded key matches the current snapshot artifact, do nothing 3) If there is no SHA1 key, or it does not match, download the module/artifact This means that the process is pretty efficient when SHA1 keys are published. But when no SHA1 keys are published, this would mean that we'd be downloading the artifacts every time*. (Users could then do cacheChangingModulesFor 24, 'hours') Thoughts? -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com * We can make the SHA1-absent process more efficient in the future, by caching the response details per URL and supplying an "If-Modified-Since" header when requesting
