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.
The ant jar in the FOP CVS was a bit customized: Keiron moved the xslt task into ant.jar and omitted optional.jar completely. I vaguely remember someone upgradesd the ant jars somewhere (HEAD or maintenance, don't recall). In any case, somebody stuck with an earlier FOP checkout might have problems...
Building FOP (HEAD) without "embedded" Ant goes like this:...
- extend you PATH variable with %ANT_HOME%\bin
or copy/move the ant scripts into a directory which is already in the path.
There is, however, the inconvenience called "FOP task" somewhere, which needs to refer to ant jars for compilation. I believe we need to fumble a bit with build.xml in order to get ant.jar into the classpath for this. I even believe the java file is currently unconditionally compiled, which seems unprudent.
Peter:
I think it points to the fact that we will have to provide a custom ant build, optional.jar and library dependencies, including junit.jar.
That's not necessary if people install a proper binary ant distro.
It's somewhat like the FOP binary distro: we provide a pre-built jar offering Jimi, JAI and crypto support, something which people building FOP from source not necessarily get.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
