I don't entirely understand all the details, but I wouldn't dismiss
shell
scripts unless you have a good reason. Shell scripts have easy
access to
$HOME, and they can end with the 'exec' builtin that chains to another
executable. In other words, if it works and has no unpleasant
side-effects, then why not use it?
I don't quite see how writing a Java wrapper would be any better,
and it
could be worse, because it probably takes longer to launch 'java'
than it
does to run a shell script.
I've still to evaluate pros and cons, but my concern is that I need
Java 5 but the original scripts (which are automatically generated by
the IDE I'm using) just use the default JDK installed in the system.
On most Tiger platform it's Java 5, but it depends if they have been
updated. If the default JDK is not good, the user would have to
manually edit a config file, which disrupts the idea of installing
the application by just dragging its icon into the Applications
folder. In any case, whenever Java 6 will be available, my
application will need it, so I really appreciate the capability of
the Info.plist to choose the good JDK and eventually give an error
message if it's not found.
_______________________________________________
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
