Bugzilla – Full Text Bug Listing
| Summary: | Oomph installer on OS X should inform the user that JDK is required | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Eric Rizzo <eclipse-bugs> |
| Component: | Launcher | Assignee: | Project Inbox <equinox.launcher-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | bruks546, Ed.Merks |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Whiteboard: | stalebug | ||
|
Description
Eric Rizzo
This failure and the instructions it produces are directly produced by the Eclipse native launcher. Oomph can't do better than that without replacing it. That's why on Windows the installer is distributed as a self-extracting executable, i.e., with its own native launcher, which behaves differently: https://waynebeaton.wordpress.com/2015/05/25/screenshot-of-the-week-missing-jre/ Certainly I would expect the Eclipse native launcher itself to be smarter. Especially on Mac there is a command to list all the known JDKs and JREs, and the launcher could be smarter about picking from those available, rather than relying purely on the default. *** This bug has been marked as a duplicate of bug 477998 *** I disagree that this is a duplicate of Bug 477998. That bug is about packaging the installer, this is about the detection of JVM and resulting instructions when one isn't found. If it's not under the control of Oomph, then please move this to whatever product/component the native launcher falls under. Reopening and re-assigning to the Equinox Launcher component. C'mon Bugzilla, re-open it. (In reply to Eric Rizzo from comment #0) > On recent versions of OS X, installing just a JRE 1.7 or 1.8 is not > sufficient to allow Oomph (or Eclipse in general) to locate it > automatically. For some reason, the JRE installation does not make it > available as the system default JVM for applications. > This manifests in many users getting a very confusing "Eclipse requires > legacy Java" message from OS X, which prompts them to install an outdated > 1.6 JVM. Then Oomph reports that it can't run because it requires 1.7. Many > users on the forums and Stack Overflow get totally confused by this cycle. > Many, many users. > > I propose that on OS X, the installer must be more specific and direct > users to install the JDK, which solves the problem. Even though neither > Oomph nor Eclipse in general strictly require a JDK, I think it's a much > better user experience to avoid the problem altogether by directing users to > the JDK. Hi, I am presenting the same problem. I am trying to download JDK from the website but I can't find it. Could you send me a link where I can download it, please. Thank you Edwing This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |