• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

eclipse, java, jmockit and mavericks

 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
reply
    Bookmark Topic Watch Topic
  • New Topic