I am only using static revisions in my dependencies, yet it still seems to be
hitting the remote repos during resolves. I do notice that the cached xmls
contain lots of evictions of "latest-revision", e.g.:
<module organisation="commons-logging"
name="commons-logging" resolver="default">
<revision name="1.0" evicted="latest-revision"
evicted-reason="" downloaded="false" searched="false" conf="runtime,
compile, master, default" position="-1">
Thanks,
L
Xavier Hanin wrote:
>
> If you are using only static versions (no latest.xx or the like) then
> resolve should be very fast once everything is provisioned in cache. If
> you
> use dynamic revisions, you can have changes in your dependencies even if
> you
> have no change in your ivy file, so comparing timestamps is not enough.
> ATM
> Ivy is always checking the remote repositories when you use dynamic
> revisions, but this may be improved before 2.0 final, by configuring some
> kind of TTL once a dynamic revision is resolved (for instance to check for
> new versions only once a day or something like that).
>
> Xavier
>
>
>
--
View this message in context:
http://www.nabble.com/how-to-ignore-missing-metadata--tp14536594p14604766.html
Sent from the ivy-user mailing list archive at Nabble.com.
