Stefan Bodewig wrote:
On Sun, 19 Oct 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
The corresponding <junit> invocation does not specifiy the
"includeantruntime" attribute, which defaults to true. So the Ant
runtime should be included in the classpath. However, the
ant-launcher.jar doesn't seem to be on the classpath here.

I'm not really sure whether it must be there, but it should be now (using CVS HEAD). includeantruntime="true" is supposed to put enough of Ant into the CLASSPATH to run Ant's JUnit testrunner, and this doesn't need ant-launcher.jar.

It used to include all of Ant in Ant 1.5.x, but this is no longer true
since we've split up optional.jar.  I've added ant-launcher.jar so
that you now should have enough in CLASSPATH to actually run Ant, but
you may find that you don't have access to any optional tasks.

Okay, thanks a lot Stefan. I'll try the change as soon as possible.

-chris



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to