PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2913 *** shadow/2913 Mon Jul 30 20:32:49 2001 --- shadow/2913.tmp.22022 Wed Aug 1 06:52:26 2001 *************** *** 2,8 **** | Java task passes incorrect memory parameter if Ant run with 1.2 JVM and jv | +----------------------------------------------------------------------------+ | Bug #: 2913 Product: Ant | ! | Status: NEW Version: 1.3 | | Resolution: Platform: All | | Severity: Normal OS/Version: Other | | Priority: Other Component: Core tasks | --- 2,8 ---- | Java task passes incorrect memory parameter if Ant run with 1.2 JVM and jv | +----------------------------------------------------------------------------+ | Bug #: 2913 Product: Ant | ! | Status: ASSIGNED Version: 1.3 | | Resolution: Platform: All | | Severity: Normal OS/Version: Other | | Priority: Other Component: Core tasks | *************** *** 77,79 **** --- 77,90 ---- [java] -noverify do not verify any classes [java] -nojit disable JIT compiler [java] Java Result: 1 + + ------- Additional Comments From [EMAIL PROTECTED] 2001-08-01 06:52 ------- + One way to handle this would be to allow for a JVMVersion attribute which could + be set to "1.1" in this case. This new attribute could be used in conjunction + with the jvm attribute. If not present, the current behaviour, to assume the + same version as Ant, would be used. + + As far as I can tell, the only attribute for which this makes a difference is + the MaxMemory attribute. If you know you are going to use a 1.1 VM, you could + use a <jvmarg> element in place of the MaxMemory attribute to set the max + memory in a way compatible with the JVM
