On 1/15/2013 9:30 PM, Shai Erera wrote:
thanks guys, that solved it.
Shai
On Wed, Jan 16, 2013 at 6:27 AM, Steve Rowe <[email protected]
<mailto:[email protected]>> wrote:
Hi Shai,
Nuking your ivy cache dir will probably fix the problem - by default
this is at ~/.ivy2/cache/.
There is a fix for this issue in ivy, just not released yet. The issue
on this side of the fence is LUCENE-4636, linked to IVY-1388.
I'm not sure what the holdup is for release of ivy 2.3.0. According to
jira, there are no open issues on that version, and this has been the
case for quite some time now.
On my systems, I checked out the ivy 2.3.0 branch, built it, and have
replaced the ivy jar in ~/.ant/lib. I haven't had this problem in a
while now, and I often ctrl-c a build because I've realized I forgot to
do something.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
