Doug Zwick wrote:
> - if and only if the user OKs it (and the file already exists),
> go in and munge ~/Library/Caches/java/deployment.properties.
The settings in that file are global to that user. They affect every
situation where Java Preferences holds sway:
1. browser applets.
2. double-clickable jars.
3. bundled apps with JVMVersion of "1.[34]+".
If explained to users that way, I suspect far fewer would agree.
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.
-- 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
