Community
Participate
Working Groups
Build Identifier: 3.6M6, I20100312-1448 The execution environment preference pane shows all JREs as perfect match for JavaSE-1.6. Happens in 3.5.2 and 3.6M6 for me. See attached screenshot. Because of this it picks 1.4 when launching with EE JavaSE-1.6. Reproducible: Always
Created attachment 163018 [details] Execution environment preference page showing all JREs as perfect match for JavaSE-1.6
Reason could be that the other JREs are not really what they pretend to be. I remember that Apple decided to throw away all old JRE during an update (I don't remember when exactly, but could have been the update to Mac OS X 10.6). After that, the older JREs were just soft links to the 1.6.0 JRE. So I guess this is in fact a NOT_ECLIPSE bug. However, most people will get into this situation with recent versions of the OS, so maybe the Mac JRE detector could be enhanced so that it omits the disguised JREs.
I'm running 10.6 and indeed, all old versions are symbol links to the current JDK: ls -la /System/Library/Frameworks/JavaVM.framework/Versions/ total 64 drwxr-xr-x 13 root wheel 442 11 Mär 09:01 . drwxr-xr-x 12 root wheel 408 11 Mär 09:00 .. lrwxr-xr-x 1 root wheel 5 11 Mär 09:00 1.3 -> 1.3.1 drwxr-xr-x 3 root wheel 102 20 Jul 2009 1.3.1 lrwxr-xr-x 1 root wheel 10 11 Mär 09:00 1.4 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 11 Mär 09:00 1.4.2 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 11 Mär 09:00 1.5 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 11 Mär 09:00 1.5.0 -> CurrentJDK lrwxr-xr-x 1 root wheel 5 11 Mär 09:00 1.6 -> 1.6.0 drwxr-xr-x 8 root wheel 272 11 Mär 07:08 1.6.0 drwxr-xr-x 9 root wheel 306 11 Mär 09:00 A lrwxr-xr-x 1 root wheel 1 11 Mär 09:00 Current -> A lrwxr-xr-x 1 root wheel 3 11 Mär 09:00 CurrentJDK -> 1.6
Created attachment 163190 [details] Fix for MacOSXVMInstallType Fixed MacOSXVMInstallType to use canonical file names to correctly resolve symbolic links and cleaned up the code a bit along the way. Unfortunately, JVMs are not rescanned for existing workspaces, is there a way to enforce this? Adding extra code to throw out the bogus entries seems a bit too far off the way.
Created attachment 163191 [details] mylyn/context/zip
Created attachment 163198 [details] Fix for MacOSXVMInstallType
Created attachment 163200 [details] Fix for MacOSXVMInstallType cleanups
Comment on attachment 163200 [details] Fix for MacOSXVMInstallType Applied patch, updated copyrights.
Applied/Fixed. Thanks Ralf.
Verified.
This was not updated by p2 when I updated to org.eclipse.sdk.ide 3.6.0.I20100414-1200, still got org.eclipse.jdt.launching.macosx 3.2.0.201003282049.
(In reply to comment #11) > This was not updated by p2 when I updated to org.eclipse.sdk.ide > 3.6.0.I20100414-1200, still got org.eclipse.jdt.launching.macosx > 3.2.0.201003282049. Just checked the Mac install here - it has the latest/correct version of the launching bundle. If you have a case where updating from one build to the next does not work, I would suggest to file a bug against Equinox/p2.
