To open Eclipse, you need to install the legacy Java SE 6 runtime.

Just installed a new version of Kepler 64bit "for Java developers" on Yosemite, getting this error on first launch. Any thoughts on how to fix it? I really don't want to downgrade my version of Java!

+42
eclipse osx-yosemite
Nov 10 '14 at 15:41
source share
6 answers

I ended up leaving and downloading Java 6:

http://support.apple.com/kb/DL1572?viewlocale=en_US&locale=en_US

Apparently, this seems to coincide with the latest version of Java that I also installed (version 8 update 25), and version 8 appears as the version that I run when I check from

https://www.java.com/en/download/installed.jsp

I don’t understand what the security implications are, but would prefer a different solution, if anyone finds a better solution than installing 6, please let me know.

+14
Nov 10 '14 at 20:35
source share

I just ran into this in another Eclipse application on Yosemite and figured out (using the links below) how to get the application to work without installing the outdated Java SE 6 JRE. Here are the steps to help other developers work with Eclipse.

BACKGROUND

$ sw_vers -productVersion 10.10.1 $ java -version java version "1.8.0_25" Java(TM) SE Runtime Environment (build 1.8.0_25-b17) Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode) 

Other configurations may work; this is my environment.

STEPS

  • Change info.plist for JDK after installation:

     $ sudo nano `/usr/libexec/java_home -V`/../info.plist 
  • Change the following section:

     <key>JVMCapabilities</key> <array> <string>CommandLine</string> </array> 

    to

     <key>JVMCapabilities</key> <array> <string>JNI</string> <string>BundledApp</string> <string>WebStart</string> <string>Applets</string> <string>CommandLine</string> </array> 
  • Try opening the application from the command line (not sure if this is strictly necessary, but what I did)

    You should receive the error message "(application) could not be opened because it is from an unidentified developer."

  • Go to the System Settings: Security Settings (General) section, and you will see the last application next to the "Open Anyway" button - click this button to open the application.

This opens Eclipse without requiring a separate download of legacy Java SE 6 files.

NOTES

When I solved this on MTGBrowser (below), I also advised changing the info.plist of the application by adding the following section to the "Eclipse" section:

 <string>-vm</string><string>/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/bin/java</string> 

However, I am not sure that this is strictly necessary. In any case, this was not enough - I also had to change the JDK info.plist and security, as described above, for a complete solution.

LITERATURE

+27
Dec 21 '14 at 19:15
source share

I ran into this problem for hours. I followed every suggestion I could find in numerous forums without success. I solved the problem by simply installing the 1.8.x JDK instead of the JRE, even though I have no desire to develop Java. I think eclipse requires this.

+23
Mar 08 '15 at 2:55
source share

I got this error when installing Eclipse on a new MacBook with macOS Sierra, version 10.12.3, which, apparently, does not have ANY java installation. I put the problem into the problem by installing java version 1.8 of the JDK and then installed Eclipse after it without any problems.

i.e. before installation

 MacBook-Pro:$ java -version No Java runtime present, requesting install. 

and after installation

 MacBook-Pro:$ java -version java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) 

TL; DR; This error may indicate that you do not have Java, and you can fix the installation of the latest version of Java instead of the "old version"

+4
Feb 22 '17 at 19:26
source share

I had JDK 7 installed on Yosemite and updating Eclipse to Luna fixed this issue for me

0
May 04 '15 at 21:59
source share

My Mac crashed and after rebooting I had the same problem. It turned out that for some reason the file /usr/libexec/java_home . After linking to /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java_home , Eclipse now starts without any complaints.

0
May 09 '15 at 7:56
source share



All Articles