Closed cyberduck closed 17 years ago
@dkocher commented
Refer to #694. Have you manually changed symlinks in /JavaVM.framework/Versions/?
3196345 commented
Yes. And I know the speel about that being officially unsuportted by Apple. However with the Kernel panics that can be created with ease in Java 1.5 by Apple there was little choice in the matter of going to Java 1.6.
Further, from my testing, changing the preference in the Java pref app is what affects the "launched" java applications. Changing the command line affects apps that are launched via "java -jar" etc. I confirmed this with my own app displaying its current Java version and was surprised to see it was reporting 1.5 until I updated the Java pref application in utilities. The Java launcher in OS X apparently uses it to decide what JVM.
CrushFTP works fine as a Java app, and from command line. Eclipse works fine as well too. Cyberduck is the only Java app not wokring fine.
lrwxr-xr-x 1 root wheel 5 May 6 17:06 1.6 -> 1.6.0 drwxr-xr-x 8 root wheel 272 May 6 17:06 1.6.0 drwxr-xr-x 6 root wheel 204 May 24 21:54 A lrwxr-xr-x 1 root wheel 3 May 6 18:07 Current -> 1.6 lrwxr-xr-x 1 root wheel 3 May 6 18:05 CurrentJDK -> 1.6
Mac Mini Core Duo 10.4.9.
--Ben
@dkocher commented
Adjust the $PATH variable in your bash shell (e.g. by editing ~/.bash_profile) to change the default Java Runtime for applications launched from the command line. Use the Java Preferences.app to change the Java version for applications packaged as a .app.
3196345 commented
That isn't my issue. I want to be using Java 1.6. I have to be to prevent Kernel panics due to bugs in Java 1.5.
Is Java 1.6 supported?
--Ben
@dkocher commented
Yes, you can choose Java 1.6 in the Java Preferences.app and Cyberduck will run using Java 1.6.
3196345 commented
OK, so what is causing all the menu's to be grayed out and not working?
I wanted to use Cyberduck, but I definitely can't anymore at this point. It used to work just fine in the past.
@dkocher commented
Please read the other tickets I referenced. Revert the changes to the symlinks in JavaVM.framework and Cybeduck will work again as advertised.
FYI, I am using Java 1.6DP from a couple weeks ago. It may be the root cause. Here is the output in console.log.
ben@crushftp.com