+1. It is cleaner. Moreover, it adds an integration test to the build.
Gilles > -----Original Message----- > From: Maarten Coene [mailto:[EMAIL PROTECTED] > Sent: vendredi 4 mai 2007 0:25 > To: ivy-dev > Subject: dependency on ivy.jar > > Hi, > > one of the things that bothers me since long is the dependency on an > external ivy.jar when trying to build ivy using Ant. > As discussed some time ago on this list, there is a solution for this > problem: > > step 1: compile "Ivy Core": these classes are the core of Ivy which > doesn't has any external dependency. > step 2: compile "Ivy Ant": these classes are the Ant tasks. They have 2 > dependencies: "Ivy Core" and Ant itself. > step 3: use the classes from step1 and step2 to resolve the ivy.xml file > from Ivy > step 4: also download the jars to the lib directory > step 5: compile "Ivy Optional": these classes are extensions of Ivy and > may required 3th-party libraries. These 3th-party libraries have been > downloaded in the previous step. > step 6: create ivy.jar (containing everything) and ivy-core.jar > (containing only "Ivy Core"). > > I tried it out and it seems to work well. > > Do you think this is ok? If no-one objects, I'll try to commit my changes > this weekend. I didn't had to change much: only 2 source files and of > course the Ant build files. > > -- > Maarten > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com
