On Thu, 3 May 2007, Maarten Coene <[EMAIL PROTECTED]> wrote: > 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:
Sounds great! Gump technically builds without downloading ivy.jar as well. Of course it does so by providing the dependencies via CLASSPATH. If you want to we can split the Gump build process into four steps that are roughly equivalent to > step 1: compile "Ivy Core": these classes are the core of Ivy which > doesn't has any external dependency. Well, you'd probably use Ant to compile them (bootstrap-ant should be enough in Gump terms, plus an XML parser). > step 2: compile "Ivy Ant": these classes are the Ant tasks. They > have 2 dependencies: "Ivy Core" and Ant itself. So it'd depend on step1 plus the dependencies of step1. > step 3: use the classes from step1 and step2 to resolve the ivy.xml > file from Ivy not necessary in Gump. > 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. More or less what the current Gump build looks like, but would depend on step2. Let me know whether you want to go that route and need some assistance. > 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"). ivy.jar >= ivy-core.jar? Or do you mean ivy.jar would contain everything except for core? Stefan
