Maarten Coene wrote:
Very strange, I don't see a reason why this shouldn't work for IvyDE.
Don't you see any error messages appear on the Ivy console in your Eclipse?
Maarten
I didn't pursue it because we only need the artifact locking for Hudson
because of the multiple executors.
So I just set the strategy to "artifact-lock" for the Hudson user, and
"no-lock" for others, which matches
how we operate.
----- Original Message ----
From: David Goblirsch <[email protected]>
To: [email protected]
Sent: Tue, March 2, 2010 4:24:35 PM
Subject: Re: Ivy + hudson CI - problems downloading artifacts, please, help
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.
