--- Antoine_Levy-Lambert <[EMAIL PROTECTED]> wrote:
> Hi Erik,
>
> you are absolutely right. If fork="no" and compiler="classic", then
> the
> compiler of the current runtime will be called with 1-1 style
> switches.
>
> So something must be done to the code so that the 1-1 compiler can be
> cal
--- "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
--- 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
tance.
> Pay attention to compile first the code which has no dependencies,
> then the
> dependent code, if you do it the other way around javac (not ant)
> will
> compile everything at once even though you have specified
> patterns.
>
> Cheers,
> Antoine
>
> -U
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
I have one other question (where I am uncertain of the "best practice").
Following along in "Java Development with Ant", in the context of
using JUnit for unit testing.
It is recommended to keep test code separate from production code in the
filesystem, using unique directory trees. This make
I'm using ant to compile my project, I really like it a lot. I'm
learning to use ant from "Java Development with Ant", it's a great book.
I notice that it gets mentioned here often, so I was wondering if
anyone could clarify something for me. Please bear in mind that I'm new
to ant when it c
