Even when everything is in your cache, there are still some cases when ivy has to look on the repository. For example, if your are using some of the x.latest, or version ranges. It is possible that it is one of your repository that occasionally took a long time to respond.
Gilles 2007/8/25, Colin Fleming <[EMAIL PROTECTED]>: > Hi all, > > We're in the process of migrating our build to Ivy, and we've noticed > that occasionally Ivy will pause for an extremely long time (minutes) > doing a resolve. This is in a build where everything is in either the > cache or a local repo, it shouldn't need to be going to the network. > If I break out and re-run the build it works fine. Has anyone > experienced this? Is there anything I can do to diagnose it? > Unfortunately since it's not repeatable it's not easy to always have > -debug on, the output is huge. > > Any help appreciated, > Colin > -- Gilles SCOKART
