https://tedvinke.wordpress.com/2013/12/17/mixing-junit-hamcrest-and-mockito-explaining-nosuchmethoderror/
This is extremely discouraging that BOTH Junit and Mockito would embed hidden transitive dependencies that are almost impossible to find without looking into the contents of the jars in the classpath.This could be due to the fact that JUnit itself brings along its own version of Hamcrest as a transitive dependency. Now if you would be using JUnit 4.11 it would depending on Hamcrest 1.3 already – see here. Getting above error would be weird – since the describeMismatch method is present in org.hamcrest.Matcher interface. --Ted Vinke
SHAME ON YOU
No comments:
Post a Comment