Oddly, I finished the article with an improved opinion of Oracle. They were willing to change the property back because of a bug in Eclipse... That's quite a bi

Oddly, I finished the article with an improved opinion of Oracle. They were willing to change the property back because of a bug in Eclipse... That's quite a bit more give than I would have expected from Oracle. Of course, it might have been wise PR as the problem only showed up after updating the JDK. It would have been easy for developers to blame the wrong party.