|
Re: Using New Installer on Mac [message #1717665 is a reply to message #1717586] |
Tue, 15 December 2015 15:42 |
|
On 12/15/2015 07:51 AM, David Akins wrote:
> In trying to use the Eclipse Installer on a Powerbook Pro running OS X
> 10.11.1,
> I get the message "Incompatible JVM" with details: "Version 1.6.0_65 of
> JVM not suitable, 1.7 or greater rerquired".
>
> Any suggestions on how the issue can be resolved would be appreciated.
> Thanks.
Not a Macintosh guy, but wouldn't this just mean it's time to bump your
JRE to a modern one? The current Oracle JRE is at 1.8. 1.6 and 1.7
aren't really supported anymore. (Apple may be different on this point,
I don't know.)
|
|
|
|
|
|
Re: Using New Installer on Mac [message #1717871 is a reply to message #1717837] |
Thu, 17 December 2015 13:27 |
Eric Rizzo Messages: 3070 Registered: July 2009 |
Senior Member |
|
|
Eike,
Are you aware that on recent versions of OS X the Oomph installer doesn't work if the user doesn't already have a JDK (not JRE) installed? They get the "legacy Java" message from OS X, but if they install that (it's Java 1.6) then the Oomph installer will run but complain that they require Java 1.7. It's a frustrating dead-end for users.
Seems like it would be worthwhile to investigate why OS X insists that the Oomph executable requires "legacy Java."
[Updated on: Thu, 17 December 2015 13:28] Report message to a moderator
|
|
|
Re: Using New Installer on Mac [message #1717886 is a reply to message #1717871] |
Thu, 17 December 2015 14:02 |
Ed Merks Messages: 33218 Registered: July 2009 |
Senior Member |
|
|
Eric,
Eike and I are both Windows users though we have virtual boxes for Mac
and Linux (Ubuntu). My Mac virtual box is unfortunately broken again.
So it's hard for us to experience the behavior of recent versions of OS
X. One has to wonder why a recent version of OS X doesn't come with a
decently recent version of Java, but that's hardly something any of us
can influence...
In any case, the behavior of the Eclipse native launcher on all the
platforms is arguably poor when the necessary version of Java of the
correct bitness isn't available. So on Windows we provide our own
native executable for launching the installer, which does a proper job
of figuring out which JVMs are available (even if they aren't on the
PATH), and properly prompts the user to install an appropriate JRE/JDK
when necessary. If we distributed the installer on Mac as a DMG and
provided a similar native executable with similar behavior to Windows,
we could definitely improve this situation. Failing that, we're stuck
with an ugly tar file and stuck with the Eclipse native launcher, along
with its associated nasty misbehavior. We're very sorry for that, but
the weeks of effort involved in improving this, working on a horrible
virtual box, is just not something we can manage...
On 17/12/2015 2:27 PM, Eric Rizzo wrote:
> Eike,
> Are you aware that on recent versions of OS X the Oomph installer
> doesn't work if the user doesn't already have a JDK (not JRE)
> installed? They get the "legacy Java" message from OS X, but if they
> install that (it's Java 1.6) then the Oomph installer will run but
> complain that they require Java 1.7. It's a frustrating dead-end for
> users.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09909 seconds