Debugging Faulty Assumptions

I wanted to install Oracle JDevelper 12.1.3 – a version that I had been eagerly awaiting. Since my primary machine is a MacBook, I wanted to install it on OS X 10.9.3.

I downloaded the generic installer and found that the install didn’t run. Since OS X had disappeared from the documentation, I assumed that I would have to fiddle around until I found a combination of JDK and OS X that worked. However, Shay Shmeltzer from Oracle assured me that OS X was indeed supported, and many friends and colleagues weighed in with OSX/Java combinations that worked for them.

I was pulling my few remaining hairs trying to get the thing running when Chris Muir helpfully provided a SHA checksum to validate my JAR file. And sure enough, theĀ  download was corrupted. It’s been ages since I last had a download complete successfully and still be corrupted, but that doesn’t mean that it will never happen again. Just like it will sometimes be true that it’s a hardware problem.

Lessons learned:

  1. Don’t fall prey to false assumptions. Because the problem looked like something I knew (the JDeveloper/OSX/Java combo has historically been temperamental), I erroneously assumed this was an instance of a specific problem.
  2. Ask for help. Lots of people have contributed their running environments and suggestions, which pushed me out of the wrong direction I was looking.