Avoid NoClassDefFoundError on JUnit Runner class #176

Closed
rliesenfeld opened this Issue May 26, 2015 · 0 comments

Comments

1 participant
@rliesenfeld
Member

rliesenfeld commented May 26, 2015

When the JRE lacks the native "attach" library and "-javaagent" is not used, JMockit initialization fails with the proper exception, but it also causes a NoClassDefFoundError for the org.junit.runner.Runner class (since it triggers initialization through the Attach API in the first place).

This secondary failure needs to be avoided, to avoid confusing the user.

@rliesenfeld rliesenfeld self-assigned this May 26, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment