Eclipse 2018-09 and Amazon Corretto [message #1798475] |
Mon, 19 November 2018 11:17  |
Eclipse User |
|
|
|
I cannot launch Eclipse using Amazon Corretto JDK (1.8) on MacOS X 10.13.6
I've been running Eclipse 2018-09 with Oracle JDK8, and also with AdoptOpenJDK 8 and 11. With Amazon Corretto 8, Eclipse fails on startup with "Failed to create the Java Virtual Machine"
I've tried the various methods in this forum and others regarding setting/unsetting things in the eclipse.ini file to no avail. No logs are produced that I can find, so I'm out of troubleshooting ideas.
Anyone else experience this? Anyone running Eclipse with Corretto?
|
|
|
|
|
Re: Eclipse 2018-09 and Amazon Corretto [message #1799280 is a reply to message #1799273] |
Mon, 03 December 2018 17:17   |
Eclipse User |
|
|
|
This is what I see:
$ /usr/libexec/java_home --verbose
Matching Java Virtual Machines (8):
11.0.1, x86_64: "OpenJDK 11.0.1" /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home
11, x86_64: "OpenJDK 11" /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
1.8.0_192, x86_64: "Amazon Corretto 8" /Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home
1.8.0_192, x86_64: "Java SE 8" /Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home
1.8.0_181, x86_64: "Java SE 8" /Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home
1.7.0_80, x86_64: "Java SE 7" /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home
1.6.0_65-b14-468, x86_64: "Java SE 6" /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
1.6.0_65-b14-468, i386: "Java SE 6" /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Ah, if I try the launcher with `-debug`, I see the following:
$ /installs/Eclipse.app/Contents/MacOS/eclipse -console -vm /Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/bin/java
Start VM: -Dosgi.requiredJavaVersion=1.8
-Dosgi.dataAreaRequiresExplicitInit=true
-Xms256m
-Xmx1024m
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-Djava.class.path=/installs/Eclipse.app/Contents/MacOS//../Eclipse/plugins/org.eclipse.equinox.launcher_1.5.200.v20180922-1751.jar
-os macosx
-ws cocoa
-arch x86_64
-showsplash
-launcher /installs/Eclipse.app/Contents/MacOS/eclipse
-name Eclipse
--launcher.library /installs/Eclipse.app/Contents/MacOS//../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.900.v20180922-1751/eclipse_1801.so
-startup /installs/Eclipse.app/Contents/MacOS//../Eclipse/plugins/org.eclipse.equinox.launcher_1.5.200.v20180922-1751.jar
--launcher.appendVmargs
-debug
-vm /Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/bin/../jre/lib/server/libjvm.dylib
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Dosgi.dataAreaRequiresExplicitInit=true
-Xms256m
-Xmx1024m
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-Djava.class.path=/installs/Eclipse.app/Contents/MacOS//../Eclipse/plugins/org.eclipse.equinox.launcher_1.5.200.v20180922-1751.jar
Error: could not find libjava.dylib
Failed to GetJREPath()
But its layout doesn't seem any different from Oracle JDKL:
$ find /Library/Java/JavaVirtualMachines/{jdk1.8.0*,amazon-corretto-8.jdk}/Contents/Home -name libjava.dylib -o -name libjvm.dylib
/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home/jre/lib/server/libjvm.dylib
/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home/jre/lib/libjava.dylib
/Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/jre/lib/server/libjvm.dylib
/Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/jre/lib/libjava.dylib
(I trimmed out the 181 from the above, as it's no different.)
[Updated on: Mon, 03 December 2018 17:17] by Moderator
|
|
|
|
|
Re: Eclipse 2018-09 and Amazon Corretto [message #1822362 is a reply to message #1821029] |
Wed, 04 March 2020 18:34  |
Eclipse User |
|
|
|
I had the same message with an AdoptOpenJDK build (11 iirc) - the problem turned out to be due to package structure changed. The MacOS\libjli.dylib file was no longer a symbolic link but a copy of the file. Seems to matter to the Eclipse launcher.. Worth checking that perhaps..
|
|
|
Powered by
FUDForum. Page generated in 0.04177 seconds