--- "Brown, Michael (Denver)" <[EMAIL PROTECTED]> wrote:
> Erik,
>
> If I am understanding your problem, I think you would want to use the
> attributes:
> memoryInitialSize
> memoryMaximumSize
>
> Based on the fact that you are forking, this makes even more sense.
>
> Hope this helps.
>
> Mike
Erik,
If I am understanding your problem, I think you would want to use the
attributes:
memoryInitialSize
memoryMaximumSize
Based on the fact that you are forking, this makes even more sense.
Hope this helps.
Mike B.
-Original Message-
From: Erik Price [mailto:[EMAIL PROTECTED]
Sent:
--- Antoine_Levy-Lambert <[EMAIL PROTECTED]> 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
>
> You might additionally need to set the "co
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
You might additionally need to set the "compiler" attribute, which tells ant
how to pass arguments to the compi
Antoine,
Thanks for responding. The approach you describe is the one that I've
taken -- two different tasks, each of which is passed a
different using a pattern criterion.
In fact, just to make it simple, I'm only attempting to compile the
1.3-compliant code (I've commented out the task for t
I think it is.
Using ant 1.5.4 (which by the way can also run under java 1.1, but this is a
detail).
- set the attribute fork of javac to true,
- set the executable attribute of javac to the 1.1 or of the 1.3 compiler
You need to have some objective criterion to decide what you are compiling
under
Hi,
Is it possible to write an Ant script that compiles some of the code
using the 1.1 JDK and the rest of the code using the 1.3 SDK?
We've taken over a project from a team that was using batch scripts for
the build. I'm trying to convert the build process to use Ant, which I
prefer for obvious
This works on Windows:
-Original Message-
From: Laurent Picandet [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 11:54 AM
To: [EMAIL PROTECTED]
Subject: Foreach and "End Of Line" delimiter
Hello,
I loaded a file in my build lik
If the EOL is the correct one for your platform, you
should be able to use 'delimiter="${line.separator}"'.
-Matt
--- Rob van Oostrum <[EMAIL PROTECTED]> wrote:
> I would say it depends on the platform you're
> running on ... Unix-type files
> use \n, Windows-type files use \r\n (or \n\r, I can
>
