-
Notifications
You must be signed in to change notification settings - Fork 239
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
Mocking of JavaFX Properties failed with java.lang.NoClassDefFoundError: mockit/internal/expectations/RecordAndReplayExecution #246
Comments
I am having the same issue with release 1.21 of jmockit. I get NoClassDefFoundErrors randomly on classes that are clearly in scope (they exist in the project itself). At first I thought it was related to classes I'm mocking, but it appears to be able to happen to any class. But it's definitely random. Works fine on my box, but not on the build machine. I haven't tracked down what the difference is. I'm reverting to jmockit 1.20, which has not given me this issue. @lauritziu Version 1.20 does not give me this problem. I'd be interested in your results of trying 1.20. |
For me, the problem is reproducible with JMockit 1.20 (and should be with any older version as well). |
That's the same for me. The first time it occurred with 1.20. I hoped, that 1.21 have fixed it. I didn't. My impression is, that happens not randomly. @aelmhorst if you execute the code above the error just happen randomly? That's strange. My environment: |
Unfortunately, this very cool framework is not usable for me at the moment. That's sad because I would like to promote it in my company. |
I've been battling with this issue, still with 1.20. My building is working now, and it may be fixed. Time will tell. Here's what I've learned: I was able to initially get the build to start running again as follows
However, I am using Jacoco for code coverage and setting JMockit as the java agent for Surefire means that Jacoco wasn't running. Finally what I did was to ensure that JMockit was specified prior to junit in the POM. That seemed to clear up my builds for today. Hopefully that fixes it. There seem to be a number of places where specifying JMockit before Junit is recommended, but according to the documentation that's unnecessary if using the |
I have the following simple test code:
The text was updated successfully, but these errors were encountered: