Take the 2-minute tour ×

I understand that the solution is to somehow make sure that Junit is loaded after hamcrest. I have an intellij project, in which I setup an external library, which contains both JUnit and JMock and hamcrest. How can I make sure that this error does not show up

share|improve this question
What is the external library that you are using? Do you have junit and/or Hamcrest elsewhere in your project? –  Kkkev Aug 22 '12 at 21:34

3 Answers 3

up vote 2 down vote accepted

You should make sure the compatibility of libraries(jars). If a class inside jar uses some method from class which is in another jar, and this used method is newly added and you are using old jar then definitely you will get java.lang.NoSuchMethodError.

share|improve this answer
  1. junit:junit:4.11 replaces the former junit:junit-dep
  2. JUnit 4.11 includes the org.hamcrest:hamcrest-core:1.3 jar as a dependency
  3. To use explicit Hamcrest matchers in tests, include org.hamcrest:hamcrest-library:1.3.
  4. org.mockito:mockito-all:1.9.x - includes an OLD version of Hamcrest, not as a dependency but wrapped within its jar. THIS is the culprit. (https://code.google.com/p/mockito/issues/detail?id=459)
  5. Put org.hamcrest:hamcrest-core:1.3 before all test dependencies
  6. Use Maven's dependencyManagement section to control all transitive versions of junit, hamcrest and mockito jars. For example spring-integration-test transitively includes mockito-all:1.9.0.
share|improve this answer

You need to import junit-dep.jar (which doesn't include the hamcrest dependency!?), rather than junit.jar. If you're using Maven on a large project, this can involve a lot of chasing to flush out all the obscure hamcrest and junit imports.

It might help that the upcoming release of junit will be compatible with hamcrest 1.3

share|improve this answer

Your Answer


