This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma 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: 32481
    
214

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.


[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
 
Have you checked out Aspose?
 
subject: eclipse, java, jmockit and mavericks
 
It's not a secret anymore!