Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid NoClassDefFoundError on JUnit Runner class #176

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

Avoid NoClassDefFoundError on JUnit Runner class #176

rliesenfeld opened this issue May 26, 2015 · 0 comments
Assignees
Labels

Comments

@rliesenfeld
Copy link
Member

@rliesenfeld 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
1 participant
You can’t perform that action at this time.