ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <>
Subject Re: why doesn't the chain stop at cache?
Date Wed, 04 Apr 2007 06:47:03 GMT
On 4/4/07, Jing Xue <> wrote:
> [ivy:resolve]   using main to resolve [ commons-logging | commons-logging
> | 1.1 ]
> [ivy:resolve] pre 1.3 ivy file: using exactOrRegexp as default matcher
> [ivy:resolve]   found ivy file in cache for [ commons-logging |
> commons-logging | 1.1 ] (resolved by ibiblioResolver):
> /home/jingxue/.ivy/cache/commons-logging/commons-logging/ivy-1.1.xml
> [ivy:resolve]   cacheResolver: revision in cache: [ commons-logging |
> commons-logging | 1.1 ]
> [ivy:resolve]   found [ commons-logging | commons-logging | 1.1 ] in
> ibiblioResolver

Yes, this is the normal behavior, maybe the log are misleading, but no
internet connection is done. Ivy remembers for each module which resolver
actually brought it to the cache, and when it resolves a module, if it finds
it in the cache and use the cache version, it logs that the module has been
found by the resolver which originally brought it to the cache.

Cache management should be deeply reviewed for the 2.0 release, so this may
change, because it causes some troubles sometimes (for example if you have
two settings sharing the same cache but with different resolvers, you will
see the 'unknown resolver' message.), but don't worry for your use case, you
can unplug your internet connection and you will see Ivy uses the cache

- Xavier

Learn Ivy at ApacheCon:
Manage your dependencies with Ivy!

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message