ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freier, Rod" <>
Subject RE: javac classpath issues
Date Wed, 05 Feb 2003 02:15:06 GMT
I've tried the fork="yes" option, and it still used the CLASSPATH in the
environment PLUS the one defined in the javac command.

I haven't verified that my problem occurs with the java task as shown
below... only the javac task.

Rod Freier
ACS Web Team

-----Original Message-----
From: Martin [] 
Sent: Thursday, September 05, 2002 5:09 PM
To: Ant Users List
Subject: Re: javac classpath issues

I always set my own classpath e.g.
    <java classname="test.Main" >
         <arg value="-h"/> 
           <pathelement location="dist/test.jar"/>
           <pathelement path="${java.class.path}"/>
(Run a class in this JVM with test.jar on the classpath)

since I dont know if I can depend on the classpath  environment ..


Martin Gainty




----- Original Message ----- 
From: "Freier, Rod" <>
To: <>
Sent: Tuesday, February 04, 2003 9:56 PM
Subject: javac classpath issues

The documentation seemed a little fuzzy on this:


When I use the classpath parameter of the javac task, the actual
classpath used is the one specified in the environment's CLASSPATH
variable PLUS whatever is specified in this parameter. 


Is that the correct behavior? 


It turns out I need to ignore the CLASSPATH environment variable in the
shell in which ant was run and give it a completely different classpath.
I can do this by simply setting the CLASSPATH environment variable to
blank right before I run ant, but that's inconvenient. 


Is there a way to get it to ignore the environment CLASSPATH entirely?



Rod Freier

ACS Web Team



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

View raw message