Eclipse Community Forums: Newcomers » OS X El Capitan: Eclipse runs but exported app requires legacy Java SE 6

Home » Newcomers » Newcomers » OS X El Capitan: Eclipse runs but exported app requires legacy Java SE 6 (Exported application requires legacy Java SE 6 runtime under Mac OS X 10.11 El Capitan)

Show: Today's Messages :: Show Polls :: Message Navigator

OS X El Capitan: Eclipse runs but exported app requires legacy Java SE 6 [message #1749189]

Fri, 02 December 2016 20:21

Larry Edwards

Messages: 4
Registered: December 2016

Junior Member

We're developing an RCP application under Mac OS X with:

Eclipse for RCP and RAP Developers
Version: Luna Service Release 2 (4.4.2)
Build id: 20150219-0600

and Oracle JDK 1.8.0_25 is installed. Eclipse 4.4.2 runs fine, but double clicking on our application (generated using the Export Product wizard) brings up the dreaded "you need to install the legacy Java SE 6 runtime" dialog.

The application will run if started from the command line using:

java -XstartOnfirstThread -Djava.awt.headless=true -jar org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar

although then we get no splash screen.

If we alter JVMCapabiities in Info.plist in /Library/Java/JavaVirtualMachines/jdk1.8.0_.../Contents adding JNI and BundledApp, then double clicking on the application will work, but we'd prefer not to force users to do this.

It seems that since Eclipse will run without modifying the JDK Info.plist, our application should be able to as well. Does anyone know what Eclipse is doing that our application isn't, and know how to fix this for our application?

EDIT: I forgot to mention that the application runs fine from within the IDE...

Thanks!

Larry

[Updated on: Fri, 02 December 2016 20:49]

Report message to a moderator

Re: OS X El Capitan: Eclipse runs but exported app requires legacy Java SE 6 [message #1749193 is a reply to message #1749189]

Fri, 02 December 2016 21:48

Eric Rizzo

Messages: 3070
Registered: July 2009

Senior Member

Does your application have its won .ini file? Have you tried adding a -vm parameter to it so ensure that it is using the JDK and not whatever the system default JRE is?

Report message to a moderator

Re: OS X El Capitan: Eclipse runs but exported app requires legacy Java SE 6 [message #1749194 is a reply to message #1749193]

Fri, 02 December 2016 21:52

Eric Rizzo

Messages: 3070
Registered: July 2009

Senior Member

Report message to a moderator

Re: OS X El Capitan: Eclipse runs but exported app requires legacy Java SE 6 [message #1749198 is a reply to message #1749194]

Fri, 02 December 2016 23:29

Larry Edwards

Messages: 4
Registered: December 2016

Junior Member

Thanks Eric,

The app does have it's own .ini file and in fact the last thing we tried was to bundle the JVM and use the -vm flag to point to it, but that didn't fix it. I'll look at those forum threads you linked to see if I can see something we missed.

Cheers,

-Larry

Report message to a moderator

Previous Topic:	frustrated about Web App start
Next Topic:	Eclipse won't open because PowerPC apps are no longer supported

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 23:05:16 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter