Stefan Bodewig wrote:
On Sun, 19 Oct 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
The corresponding 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 Sun, 19 Oct 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> The corresponding 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 classp
On Sun, 19 Oct 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> The corresponding 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 classp
Hi all,
I'm trying to run the Cactus build with Ant 1.6beta2 and have
encountered a problem: we're using JUnit test cases that setup Ant
projects from build files to test custom Ant tasks, similar to what is
done by the Ant build itself.
The base test case class is here:
http://cvs.apache.org/v