Josh big thanks!
I switched back to 2.3.0 and everything is working fine!
@IVY Team: you should remove 2.4.0-rc1 from the latest stable release.
From my point of view there are to many major bugs in 2.4.0-rc1
bye at all helpers and have a nice weekend
Hmm, had to track through our issue: https://github.com/sbt/sbt/issues/1356
https://issues.apache.org/jira/browse/IVY-1457
https://issues.apache.org/jira/browse/IVY-1467
Hope that helps!
On Fri, May 30, 2014 at 8:48 AM, hkais...@googlemail.com wrote:
> Josh, thank you!
> Hmm, crap, we use Ec
Josh, thank you!
Hmm, crap, we use Ecplise Kepler and it is packaged with ivy 2.4.0-rc1.
I will give it a try to go back to 2.3.0.
Which of my issues are known to be bugs?
Do you have references to the bugtracker of ivy?
Thank you!
I have not known, that I can do anyway a report on broken resolve.
This helps a lot
This is a known issue with Ivy 2.4.0-RC1. We ran into this with sbt and
had to back down to ivy 2.3.0. There was a fix submitted to trunk, but I
haven't tracked the state these past two weeks to see where it is now.
Hope that helps!
On Fri, May 30, 2014 at 6:20 AM, hkais...@googlemail.com wr
Try to run an . You will need to first, but you can
add a parameter to the not to halt on failure. This will list who
is calling what dependency. I suspect that properties are being used to help
resolve the dependencies and some property isn't set correctly.
--
David Weintraub
qazw...@gmail.
Can really anyone help me out?
Hy Carsten!
At the moment all projects use "latest.integration" as revision. You can
view my ivy.xml file Online, for example:
https://github.com/AndreasFagschlunger/O2Xfs/blob/master/at.o2xfs.operator/ivy.xml
As you can see I also use the default resolvers and do not define any
resolvers by mys
