Andrew Hart wrote:
>This actually turned out to be the problem. There's some sort of
>character encoding issue at work here. I need to go back and
>re-verify that I didn't cut and paste this into the JarBundler, or
>whether or not it was JarBundler itself that inserted it, but that's
>why my bootclasspath is not working. Actually, looking at it again,
>I'm pretty sure it was JarBundler that was the culprit, because I
>didn't add the options for min and max memory sizes... those were added
>here by entering those values into the JarBundler dialog.
To find the culprit, I think you'll have to reconstruct exactly what you
did in Jar Bundler, and probably the manual steps taken thereafter. If it
really matters to you.
I just tried Jar Bundler here, on 10.4.2 with the J2SE 1.3/1.4 Release 2
installed, and it worked fine. The VMOptions key had no weird things in
its value. I typed values into each of these Jar Bundler fields under the
Properties tab:
Heap Minimum Size: 128
Heap Maximum Size: 192
VM Options: -Xbootclass:foo
The last one is gibberish, but it still appeared well-formed in the
VMOptions key, along with well-formed -Xms and -Xmx values. I dumped the
file with 'hexdump -C'.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
