> -Original Message-
> From: ippi [mailto:[EMAIL PROTECTED]
>
> Oops - spoke too soon! [red-faced grin]
>
> Without going into the embarressing details, my
> previous assertion that setting
> includeantruntime="no" made everything work
> perfectly is not at all correct. Rather, ant
> just
Oops - spoke too soon! [red-faced grin]
Without going into the embarressing details, my
previous assertion that setting
includeantruntime="no" made everything work
perfectly is not at all correct. Rather, ant
just prints out the following exception for
each TestCase loaded:
[junit] Except
Stefan, you're a Legend - the following works
perfectly (with ant 1.6.2):
wrote:
> On Fri, 21 Jan 2005, ippi <[EMAIL PROTECTED]>
> wrote:
>
> > Thanks for the reply. I had actually tried setting
> > the build.sysclasspath but I quickly gave up on it
> > when it failed to work for me. When I go
On Fri, 21 Jan 2005, ippi <[EMAIL PROTECTED]> wrote:
> Thanks for the reply. I had actually tried setting
> the build.sysclasspath but I quickly gave up on it
> when it failed to work for me. When I got your
> message I did some more extensive testing and now
> I realise that the build.sysclasspa
Hi Stefan
Thanks for the reply. I had actually tried setting
the build.sysclasspath but I quickly gave up on it
when it failed to work for me. When I got your
message I did some more extensive testing and now
I realise that the build.sysclasspath property only
effects the tasks that don't fork
On Wed, 19 Jan 2005, ippi <[EMAIL PROTECTED]> wrote:
> I was wondering if there is a way to
> get a task which contains a
> to ignore the CLASSPATH
> enviromental variable altogether.
If you can get the rest of your build file to work without CLASSPATH
as well, then you can set build.sysclass
