This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes Blog around the Campfire and the fly likes eclipse, java, jmockit and mavericks Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Other » Blog around the Campfire
Bookmark "eclipse, java, jmockit and mavericks" Watch "eclipse, java, jmockit and mavericks" New topic
Author

eclipse, java, jmockit and mavericks

Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30580
    
154

Upgrading was less than smooth. It's a mix of Mavericks and JMockit that were the source of the trouble. If Apple had left my JVM alone, the problem wouldn't have manifested. The code would have worked due to the "miracle" that had it working before. And if JMockit wasn't so finicky, this never would have been an issue.

Really? IT needs tools.jar in the classpath on a Mac. And needs to be in the classpath before JUnit. Picky mock library.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
 
GeeCON Prague 2014
 
subject: eclipse, java, jmockit and mavericks