ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Price <>
Subject Re: AW: AW: two diff't JDKs
Date Mon, 27 Oct 2003 19:29:39 GMT

--- Antoine_Levy-Lambert <> wrote:
> 1) ant cannot guess where the java 1.1 compiler is. If you want to
> compile
> with java 1.1, you have to give
> ant the full path of the compiler in the executable attribute of the
> javac
> task
> <javac executable="c:/jdk1.1/bin/javac.exe" ... />
> You might additionally need to set the "compiler" attribute, which
> tells ant
> how to pass arguments to the compiler.

I never noticed that attribute before.  Much thanks, that is exactly
what I was trying to describe earlier.
(Incidentally, Ant says that the "compiler" attribute gets ignored if
"fork" is set to true, and in order to use the "executable" attribute,
you have to set "fork" to true.)

> 2) to avoid out of memory errors, set ANT_OPTS in your environment
> export ANT_OPTS="-Xmx128M -Xms64M" for instance
> (this only applies if you are starting ant from the command line; if
> you are
> starting ant from within an IDE I do not know)

Indeed, I am trying from the command line but I wonder if there is a
way to confirm that this environment variable is being propagated into
Ant when I run Ant?  I set this environment variable but it doesn't
seem to have any effect on the output of a <echoproperties/> task
(which is usually what I use to gauge my Ant settings).  And even with
the value set to "-Xmx512M", I run out of memory, so I wonder if
perhaps it's not getting picked up?  Any suggestions?  (I'm on Win2K.)

Warm regards,


Copyright.  Copy right.
The right to copy.  That's all it is.
Contrary to popular belief, there's no such thing as intellectual "property".

Do you Yahoo!?
Exclusive Video Premiere - Britney Spears

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

View raw message