Hi, ATM Ivy is provided in the form of two jars: ivy.jar and ivy-core.jar. The ivy-core.jar is basically the same as ivy.jar except that it doesn't contain Ant related classes (mostly Ivy Ant tasks). This was introduced a long time ago for IvyDE, as a workaround to a classloader issue when contributing ivy.jar to ant classpath in eclipse.
The downside of this is that most people do not understand the difference between the two, and I often see people putting both ivy.jar and ivy-core.jar in ant/lib. Not that much a problem, until someone change only one jar out of the two, which can lead to strange bugs difficult to diagnose if ivy-core.jar is before ivy.jar in the classpath. Moreover, in recent tests I've found that the eclipse ant classpath problem was still present in some cases, and preferred to use an easy and straightforward solution: configure ant classpath manually in eclipse to add ivy.jar (or point to another ant home where ivy.jar is already present). Thus I'm wondering if it wouldn't be easier to abandon ivy-core.jar, and tell IvyDE users they have to configure their ant classpath manually IF they want to use Ivy tasks in their ant build from eclipse (as they have to do for any other custom ant tasks anyway). WDYT? Xavier -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
