On Fri, Dec 12, 2003 at 03:32:35PM +0100, Jeremias Maerki wrote: > Nope. With the Ant installation (binary, I've never had to build Ant > myself, yet) you get a fully operational optional.jar with has a usable > JUnit task as soon as you have junit.jar in %ANT_HOME%/lib. > > Building FOP (HEAD) without "embedded" Ant goes like this: > - Install Ant binary distribution > - set the ANT_HOME environment variable > - extend you PATH variable with %ANT_HOME%\bin > - Download JUnit and put the junit-<version>.jar into %ANT_HOME%\lib (if > you want to run the testcases) > - Download FOP from CVS > - go to the xml-fop directory and run "ant" or "./ant.sh"
I did that and it works fine. Until now I have been confused about ant. That may have been caused by the embedded ant jar files in many projects, and their possible incompatibility. That makes that you rely on their build script, and do not think about it. I every project requires one to obtain and install a reasonably recent ant, and avoids incompatibilities with that, a developer quickly gets up to speed with it. Similarly with adding junit or other supporting packages. Building C projects seems easy: ./configure, make, make_install. But that is only the case if the whole tool chain is present in the system. The same here. Having to have ant and junit seems a reasonable requirement, provided no project requires one to have their own ever so slightly tweaked embedded version. Regards, Simon -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
