On Dec 4, 2007 5:23 PM, Ted Kosan <[EMAIL PROTECTED]> wrote: [snip] > My solution to this problem is to simply bundle a copy of the desired > version of JavaSE, with the desired version of Java3D already > installed in it, with the application. The app is then tested against > this configuration and known to work with it. > > From what I've seen, having users simply download one archive file, > unzip it, and execute a launch script is the simplest most > trouble-free way to distribute a large Java application to users :-)
While this is indeed standard practice on Windows and Linux, my experience with applications for the Mac that bundle jars is different. The typical practice I've seen is to use the system Java, put the jars within the application subtree, typically at Foo.app/Contents/Resources/Java, and specify an application-specific classpath in the file Foo.app/Contents/Info.plist. This seems to be the recommended approach; more information on this is available at http://developer.apple.com/documentation/Java/Conceptual/Java14Development/ under "Java Deployment Options for Mac OS X". regards, Steve --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
