It would make a lot more sense to me if a compelling double-
clickable jar
offered to turn itself into a bona fide app-bundle, and then set
1.5* only
on itself. This isn't as complex as it might seem, and once you
make the
program that does it, it's widely reusable. A moderately capable
programmer should be able to do it in a single rainy weekend.
One simple strategy: exec() /bin/sh, and feed parameterized lines
to its
stdin from a script kept as a jar-resource. A few mkdir's, cp's,
chmod's,
and Voila, a bedraggled shipwrecked wench in a strange land becomes a
respected courtly gentleman.
That suggests another way of dealing with the situation -- finding the
path to the 1.5 JVM and exec-ing an appropriate java command to relaunch
the current app under 1.5. You can get the CLASSPATH and BOOTCLASSPATH
from the system properties, you know your main class implicitly, and you
can easily copy the command line args from your main routine. It might
be problematic to get the -Xmx and -Xms heap size values (the Runtime
method to get the max heap size is 1.4+ only, and returns a too-large
value, at least on my Macs) or any -D property specifications.
_______________________________________________
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
