Task #12133 (closed)
Opened 10 years ago
Closed 9 years ago
Bug: Mac versions of Insight broken on new MacOS X versions
| Reported by: | rleigh | Owned by: | jburel |
|---|---|---|---|
| Priority: | major | Milestone: | 5.1.0 |
| Component: | Insight | Version: | 5.0.0 |
| Keywords: | java8 | Cc: | spli, ux@…, java@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Running Insight on MacOS X 10.9 results in the following message:
Software Update: To open "OMERO.insight," you need a Java SE 6 runtime. Would you like to install one now?
Given that 10.7 and 10.8 are the supported versions, and 10.6 is obsolete, this is far from ideal. No security support for over a year, with no general updates for three years... The system in question had the latest 10.7 and 10.8 jdks installed. Installing 10.6 on a brand new system is not a good idea *at all*. It's one of the most exploited pieces of software on current systems, and it's a massive disservice to require our users to install it.
Could Insight be made to use 10.7? If not, could we make a separate zip release for current systems?
Change History (5)
comment:1 Changed 10 years ago by spli
- Cc spli ux@… java@… added
- Keywords java8 added
- Milestone changed from Unscheduled to 5.0.4
comment:2 Changed 10 years ago by spli
It's possible this is a bug in how the JDK is installed:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=411361#c20
http://stackoverflow.com/questions/10352715/how-do-i-run-eclipse-using-oracles-new-1-7-jdk-for-the-mac
This requires a reboot so I haven't tested it yet.
comment:3 Changed 10 years ago by jamoore
- Milestone changed from 5.1.0-m3 to 5.0.4
Moving all Java8 issues to the clean 5.0.4 milestone
comment:4 Changed 10 years ago by jburel
- Milestone changed from 5.0.4 to 5.1.0
Moving to 5.1, to be discussed with dropping 1.6 support
comment:5 Changed 9 years ago by jburel
- Resolution set to fixed
- Status changed from new to closed
I've just run into this. I've got Java 8 installed as the system default, and I don't remember seeing it with Java 7, so probably a Java 8 specific bug?