I just tried to start up my Eclipse environment only to get a window I'd never seen before, that started off with: "JVM terminated. Exit code=13".
Since this was on Windows, I checked my JAVA_HOME path variable and it looked fine, pointing to "C:\Program Files (x86)\Java\jdk1.6.0_25\bin". So that looks like the version would be 1.6, right?
Yeah, not so much. I typed "java -version" in a CMD window and got 1.8....?! Again with the wth... Apparently when I let the last Java update apply itself, it bumped the version up to 1.8 and added "C:\ProgramData\Oracle\Java\javapath" to my path statement. It then created three symbolic links to files in "C:\Program Files (x86)\Java\jre1.8.0_25\bin\". Fortunately, it left the old version in place, so all I really had to do was get those symbolic links out of the way.
Since I wasn't comfortable deleting files if I didn't have to -- in case deleting them jacked up the system -- I just renamed the "javapath" directory to "javapath_1.8". Since that exact directory isn't in the path environment variable, and the old directory still is, now when I run "java -version" I get 1.6. Fire up Eclipse and now it comes up just fine.
Look, I love being on the latest version of everything, but in this case, and until Eclipse catches up, I'm just going to have to remember not to allow Java to update itself, and when I forget, this is a handy way to straighten everything out quickly and easily.
Copyright (c)2014 Todd Grigsby, all rights reserved