To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115180
------- Additional comments from [email protected] Sat Oct 23 23:47:27 +0000 2010 ------- See also: Apple Developer: Technical Q&A QA1170: Important Java Directories on Mac OS X http://developer.apple.com/library/mac/#qa/qa2001/qa1170.html <cite> Q: I am porting a Java product to Mac OS X. What are the equivalents for directories and paths common to JDK installations on other platforms? A: Since a JDK is preinstalled on every copy of Mac OS X, the location of the Java VM may vary, but can be found using tools built into the OS. User input should never be required to locate Java-related paths and directories. Java Home Many Java applications need to know the location of a $JAVA_HOME directory. The $JAVA_HOME on Mac OS X should be found using the /usr/libexec/java_home command line tool on Mac OS X 10.5 or later. On older Mac OS X versions where the tool does not exist, use the fixed path "/Library/Java/Home". The /usr/libexec/java_home tool dynamically finds the top Java version specified in Java Preferences for the current user. This path allows access to the bin subdirectory where command line tools such as java, javac, etc. exist as on other platforms. The tool /usr/libexec/java_home allows you to specify a particular CPU architecture and Java platform version when locating a $JAVA_HOME. Another advantage of dynamically finding this path, as opposed to hardcoding the fixed endpoint, is that it is updated when a new version of Java is downloaded via Software Update or installed with a newer version of Mac OS X. For this reason, it is important that developers do not install files in the JDKs inside of /System, since the changes will be lost with subsequent updates by newer versions of Java. To obtain the path to the currently executing $JAVA_HOME, use the java.home System property. </cite> Apple Manpage to java_home: http://developer.apple.com/library/mac/#DOCUMENTATION/Darwin/Reference/ManPages/man1/java_home.1.html How does OpenOffice determine $JAVA_HOME so far? This official and recommended way? When not this recommended (because most flexible and future-safe) way, why not? Maybe that is the way NeoOffice does it (and has no troubles)? Maybe a good starting point for a fix of the issue in OpenOffice? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
