incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Commented: (IVY-380) Ivy should force cache refresh on artifact retrieval, to get past caching proxies
Date Tue, 09 Jan 2007 20:05:27 GMT


Xavier Hanin commented on IVY-380:

I agree that this is a problem, but I don't know if following usual caching rules would be
good. I think that being able to build offline is a good thing, and as long as you don't use
dynamic versions in your ivy file, if you have everything in cache, you can use Ivy cache
for as long as you want, and I think it's better like that.

On the other hand, the problem is that for the moment the only thing you can do is to say
that the cache is always or never trusted. A huge improvement would be to be able to define
a time during which cache is trusted, maybe even define that by patterns, and also be able
to force a refresh with a simple system property.

What do you think?

> Ivy should force cache refresh on artifact retrieval, to get past caching proxies
> ---------------------------------------------------------------------------------
>                 Key: IVY-380
>                 URL:
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: Steve Loughran
>            Priority: Minor
> I can't resolve stuff 
> [ivy:resolve]   problem while downloading ivy file:
to /tmp/ivy8652xml: invalid sha1
> [ivy:resolve]           module not found: [ org.apache.ant | ant | 1.7.0 ]
> The Sha1 was wrong, but it has been fixed now, but the old file is hanging around in
cache. I have to purge the entries by hand using firefox shift-reload.
> If ivy did its gets with a Cache-control header that specified the max age for a cached
artifact, we wouldnt have this problem. either we should have a default "60 minutes" or some
way to force it a full refresh.
> see :

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message