RE: Out of memory with javac

Darin: Can you isolate a particular java program that causes this out of memory exception? Are there a lot of files to troubleshoot? Mani -Original Message- From: Darin Swanson [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 4:09 PM To: Ant Users List Subject: RE: Out of memory

command line args to ANT

hey i would like to supply on the command line an arg for the ANT script -classToRun=blah and in my script, if its supplied on command line then $classToRun= that value , but if its not supplied then $classToRun=defaultClass how can this be done with if/elses for ? Thanx in advance -

RE: Out of memory with javac

It works fine on 1.4.1_07 I have only a certain set of VMs that I can get my hands on due to restrictions imposed by my employer :-) so I cannot get 1.4.1_02 or 1.4.1_03 I was testing on 1.4.2_03. and 1.4.2_04; both fail. Darins "Peter Bulford" <[EMAIL PROTECTED]> 05/25/2004 12:37 PM Plea

RE: Out of memory with javac

Hi Darin. I don't have your answer however I'm curious if your problem works fine on 1.4.1_02 and does not work on 1.4.1_03. Pete Bulford -Original Message- From: Darin Swanson [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 3:10 PM To: Ant Users List S

RE: Out of memory with javac

Thanks NetaB...but I don't think you helped me at all :-) I have fork set to be true so memorymaximumsize and memoryinitialsize should not be ignored. The main thrust of my question is why the difference running on the two implementations of javac? Works fine on 1.3.1, 1.4.1. Does not work on

junit-task and TestSetup decorator

Hi! I've searched the web and the mailinglist for a rather simple problem, but couldn't find an answer. Is it possible to use a junit.extensions.TestSetup around a fileset of junit testcases? i.e.: At this point it is not possible to disting

RE: Propery override in ant 1.6.1 vs 1.4.1

Hello, One thing to add, in Java Development with Ant page 71, Erik Hatcher points that breaks the rule of properties' immutability and advices of not relying in this hole, since it might be fixed as it is now. Ivan --- "Oleg S. Estekhin" <[EMAIL PROTECTED]> wrote: > Hello > > The properties in

RE: Propery override in ant 1.6.1 vs 1.4.1

Hello The properties in Ant 1.6 are immutable (see the second paragraph at http://ant.apache.org/manual/CoreTasks/property.html). You will have to use different property in each condition. > -Original Message- > From: Hedstrom, Brian [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 25, 200

Propery override in ant 1.6.1 vs 1.4.1

Hello, I just upgraded my Ant module from 1.4.1 to 1.6.1 and am having build problems. In particular, I traced a problem down to a set of condition statements as shown below:

loadproperties != property

Hello! I am using ant 1.5.4 and my loadproperties tasks behaves deifferently from my property tasks (when loading from a file). In particular I can specify empty properties using the property task like this: foo = When specified like this in a file and loaded with a property task the property f