I updated my mac laptop to mac OS High Sierra. In order to run my Photoshop CS3 program i have been asked to download 'legacy Java SE 6.

@Working Stiff - you think you've got it bad. I talked my wife into getting a mac after having been on them since around '86. Problem is, she needs windows for a few things concerning real estate and our finances. After a few yrs of upgrading Parallels, upgrading windows, and upgrading OS X's, she's about to throw in the towel!

I'm tech-y, but wow, after this recent misaligned trifecta of Para 10, Win 8.1, and Yosemite, I'm in her corner! And I agree, why does Apple push and promote before the OS X is ready for PrimeTime. I would have thought that I would learn by now to wait at least six months before performing any APPLE software upgrades. There's always a problem that sets me back hours if not days of productivity just trying to cycle through the endless errors and incompatibility issues with a freakn upgrade. We pay a lot of money for your products and your service level continues to decline rapidly. Because of the type of business that I'm in I'm almost forced to work with only MAC. However, I am seeking alternatives to my media production dilemmas because APPLE, I'm losing money every time you pull this crap.

We are not your BETA testers! We are hard working people trying to make a living with our investments.

Get your act together APPLE. Your trick did not work for me.

I bought a new MBA this week and transferred my files using Migration, as soon as I booted up, I got the same dialogue box. I upgraded to Java 8 and then your trick. The problem is that i don't have any applications that require Java runtime except for browsers. The only way I can get rid of the box is to start up in Safe Mode.

I've had a lot of problems with 1010. In fact, it really suc. When I received my new MBA, it still had Mavericks on it! I had to spend an hour upgrading the System before I could transfer files! I should of learned, Also, that too never, I mean NEVER, upgrade OS until all the bugs have been worked out Now I have to spend an hour on the phone with the geniuses at apple to solve this issue. Apple Footer • This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums.

Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.

Share on Facebook Tweet this Share Despite the sheer amount of unfledged devotion Microsoft’s flagship e-mail client since it arrived on Windows computers in the mid-’90s, there’s more than just one capable offering on the market for sending and retrieving email. Desktop email clients are an absolute necessity in today’s digital age, designed to access email messages regardless of an Internet connection and provide a convenient means for simultaneously accessing and consolidating multiple email addresses under one, banner application. Fee for gmail mac 2018.

Compiling to Java 8 and running on JVM 8 are two different things. The issue is not what the code is compiled with but the script within the Mac package that works out what JVM is installed and runs it. It doesn't pick the JVM version based on the language version of the JAR file. On the Mac it is not sufficient to have the JRE 1.8 installed as that just has provides a browser plug-in.

To run BEAST or Tracer or any other Java desktop program it is necessary to install the JDK. The Apple Java 1.6 install still works fine and is easier than the JDK 1.8 install. Probably the best solution (and one I will look into for FigTree also) is including a JVM within the Mac application package. So - I would absolutely be against compiling the code to Java 8 language unless there was an absolutely compelling case that the language features it brings are worth it (possibly for a newly written package but not for old code, I suspect). I see no point in making the JAR incompatible with older JVMs just for the sake of it.