Issue: http://issues.gradle.org/browse/GRADLE-2146
Summary: ‘Gradle should use last modified date to avoid artifact re-download 
where SHA1 checksums are not published’

A couple of questions…

It looks like this is going to need a new version of the artifact cache. We are 
going to need to store last modified date (probably as “publication date”) of 
the artifact as it was advertised when we obtained it and we don't currently do 
this, so we'd have to add a field to ArtifactResolutionCacheEntry. Another 
option would be to version ArtifactResolutionCacheEntry and customise the 
deserialisation, but I'd rather not go down this path. What are the 
implications of a new cache layout? What do I need to do besides bumping the 
number and updating ExternalArtifactCacheBuilder?

My plan is to push a wrapped ExternalArtifactCache into each transport that is 
scoped to the right repository and probably add new methods that implemented 
searching the cache by checksum and last modified. Any objections to this?


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to