still leads to the $CLASSPATH being
searched:
...
My current environment is a bit too complicated to
be used to debug this issue so I'm going to take
a while to set up a clean-room enviroment where I
can isolate the problem a little better.
--- ippi <[EMAIL PROTECTED]> wrote:
&
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
> >
x27;t fork a new JVM.
It's certainly a solution that I can work with but if
there was a way to achieve the same result with
fork="yes" then I would very much like to know of it.
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On Wed, 19 Jan 2005, ippi <[EMAIL PROTECTED]&
Hi,
I was wondering if there is a way to
get a task which contains a
to ignore the CLASSPATH
enviromental variable altogether. I've
tried using the fork and newenvironment
attributes in addition to the env,
sysproperty and jvmarg nested elements
but nothing seems to prevent the
CLASSPATH from
