Thomas Vatter wrote:
>2. if I don't bundle the JRE I cannot assure the the application is run
>with the JRE that it was tested with. therefore the best way is calling
>a fixed java.exe in a subdirectory.
You can't do that on Mac OS X. It's simply not possible. Accept it. You
don't have to like it, just accept it. Your only other options are in not
adapting to what is possible:
A) don't ship on Mac OS X.
B) wait for Apple to adapt to you, while doing A.
Once accepted, you can move on to how you will adapt to what's possible on
Mac OS X. You could, in approximate order of difficulty:
1) declare a required JVM version in your app-bundle's Info.plist.
2) check for a required JVM version in your Java code.
3) port an open-source JVM to Mac OS X.
#1 assumes you're distributing your app as an app-bundle. It's the
JVMVersion key.
<http://developer.apple.com/documentation/Java/Conceptual/JavaPropVMInfoRef/Arti
cles/JavaDictionaryInfo.plistKeys.html>
#2 is easy to do, but informing the user how to remedy the situation takes
a moderate amount of GUI design.
#3 is decidely non-trivial, and the time-lag may approximate the
non-adapting option B.
By the way, another option to shipping a specific JRE is for you to test on
a variety of JRE's. That is, your program is adapting itself to what JRE
it finds, rather than asserting its JRE as the one thing it works on. That
again is an adaptive strategy, not an assertive one.
-- 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
