Yes, my ivyconfig is available locally. The last line output before the timing information is:
[ivy:configure] setting 'ivy.default.always.check.exact.revision' to 'false'. // delay [ivy:configure] configuration done (97962ms) [ivy:configure] default cache: /home/crahen/.ivy/cache [ivy:configure] default resolver: online [ivy:configure] default latest strategy: latest-revision [ivy:configure] default conflict manager: latest-revision [ivy:configure] circular dependency strategy: warn [ivy:configure] validate: true [ivy:configure] check up2date: true My project has no dependencies. <chain> <cache/> <filesystem/> <ur/l> <url/> </chain> On 12/26/06, Xavier Hanin <[EMAIL PROTECTED]> wrote:
On 12/24/06, Eric Crahen <[EMAIL PROTECTED]> wrote: > > Using version 1.4.1 I've notived that ivy:configure takes an extrodinarily > long time. I have 1 resolver > configured, which is a local filesystem resolver and ant -d shows > ivy:configure took 26700 ms on average > on the last three runs. This is very strange. Is your ivyconf.xml file available locally? If not can you try with a local file? When you run it in debug mode, do you see a pause at some time? What is the last output before the pause? Xavier > Verbose ant trace doesn't show anything further. The > last line I see before the timing > information is: > > ivy.default.always.check.exact.revision being set to false. > > -- > > - Eric > >
-- - Eric
