ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: problem with the java needed urgent
Date Fri, 05 Sep 2003 12:18:52 GMT
Hi Stefan,

 My classpath consists of so many different directories involved which is why it is so long.
In my ant build script file I am just giving $classpath but how about in command line ??.
I think I can't go more than that 2046 even when I declare all my classpaths in Window's user
variable or env variable Classpath..

 Regarding fork, how can I pass environment variables without using jvmarg for which fork
is needed to be set true. Any other keyword ??


-----Original Message-----
From: ext Stefan Bodewig []
Sent: 05 September, 2003 15:06
Subject: Re: problem with the java needed urgent

On Fri, 5 Sep 2003, Laxma Nandikonda <>

> 1. How can I overcome this problem of too long command line.

Don't fork.

Use $CLASSPATH instead of expanding it.

> I have this dependcies target rmic depends compile1 target compile1
> depends init target init depends clean
>   and then a separate target run.
>   It's saying the complete build sequence is [run, clean, init,
>   compile1, rmic]. I think rather it should say [run, rmic,
>   compile1, init, clean ]. Any comments ??

You are reading the output in the wrong direction (and the output is
misleading as only the build sequence is important to you, the
"complete" build sequence is something internal to Ant).

run, clean, init, compile1, rmic

means not much - if your invoke "ant run", run will be the only thing
that gets invoked.  The order of clean, init, compile1, rmic matches
exactly your dependenvy chain - this is the order the targets would
get executed in if you invoked "ant rmic".


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message