I did a little investigation into this, i.e. I did a cvs checkout of the source, and noticed that someone added a "maxmemory" attribute to SignJar on 12/23.

<hat style="manager">
I did not, however, find a bug entry for this. Not yet having contributed to an open source project, is it standard practice for the opensource community to just submit code fixes without recording bug/enhancement entries in bugzilla? On projects I have been on in the past, as my current project, we submit enhancement entries such that changes like this can be logged.
</hat>


<hat style="qa">
Why was the attribute not named "memoryMaximumSize" as it was for javac for consistancy purposes?
Why was a "memoryMinimumSize" attribute not added, again for consistancy?
Why was the Java class attribute not made all lower case to match the rest of the source in the file?
</hat>


Regardless, is there anyway to check on the status of this fix and its possible inclusion in 1.5.2 or 1.6?

Thanks,

-Jim

P.S. Sorry about the <hat> tags, the person that suggested that has been sacked.

Date: Tue, 14 Jan 2003 07:18:44 -0600
From: Jim Garacci <[EMAIL PROTECTED]>
Subject: signjar task OutOfMemoryError
Content-Type: text/plain; charset=us-ascii; format=flowed


I am using the signjar task, Ant 1.4.1, and am getting an OutOfMemoryError.

I see that jarsigner on the command line requires VM options to be passed using -J-Xms128m -J-Xmx256m arguments. Is there a way to do this in the signjar task. Or in all ant tasks, in general?

Note: setting ANT_OPTS does not work. I have that set to 128m and 256m already, which works for compilation using javac. However, jarsigner is not passed these and fails.

Thanks in advance,

Jim



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



Reply via email to