David Goblirsch wrote:
Maarten Coene wrote:
ok, I've found a place in the Ivy code that could cause the resolve
to hang.
I've fixed that particular problem in SVN trunk. Could you try again
with the latest Ivy code from trunk to see if the problem has been
fixed?
thanks,
Maarten
Fixed! I downloaded the jar 2.2.0.20100227220116.jar from your Hudson
server, and it worked. Thank you so much.
David
However, we just discovered that having that setting,
<caches lockStrategy="artifact-lock" />
breaks the resolve in IvyDE 2.1 on Eclipse 3.5R1 (JEE version) even
using the new pre-release jar.
That is, clicking on ivy.xml[*] to "Resolve" produces nothing, leaving
the build path empty.
----- Original Message ----
From: David Goblirsch <[email protected]>
To: [email protected]
Sent: Fri, February 26, 2010 12:28:30 AM
Subject: Re: Ivy + hudson CI - problems downloading artifacts,
please, help
Maarten Coene wrote:
I was not aware of any problems with the artifact-lock strategy.
Could you provide more details, like for instance the ant output
when setting the property "ivy.log.locking" to "true"
Maarten
If I put this line
<caches lockStrategy="artifact-lock"/>
into my Ivy settings file, and then start with a clean slate, i.e,
having completely cleared the local cache under .ivy2,
and then run ant 1.7.1 with -Divy.log.locking=true as you suggested,
I see that
ant ends up in an "infinite" loop printing out log messages that say
Thread[main,5,main] [large integer] file creation failed [filename]
