Junit4: Hamcrest-all 1.3 with JUnit 4.11 throws exception
Hi,
In the ExpectedException class there is this import:
import static org.hamcrest.CoreMatchers.containsString;
which cannot be resolved if you use hamcrest-all simply because the containsString method is in org.hamcrest.Matchers.
hamcrest
apreg
All 4 comments
Ah, false report. It turned out the mockito-all 1.9.5 has hamcrest integrated in which caused the problem. Sorry.
apreg
on 9 Apr 2014
👍1
@apreg , how did you solve this issue?
vlio20
on 6 Feb 2018
sorry, I cannot remember
apreg
on 6 Feb 2018
You should always avoid to use hamcrest-all together with JUnit because hamcrest-all contains classes of hamcrest-core. Please use hamcrest-library if you need more than the core matchers.
stefanbirkner
on 8 Feb 2018
👍2
Was this page helpful?
0 / 5 - 0 ratings
Related issues
gonzen
·
7Comments
kluever
·
16Comments
cardil
·
9Comments
kcooney
·
108Comments
sbrannen
·
22Comments
Most helpful comment
You should always avoid to use hamcrest-all together with JUnit because hamcrest-all contains classes of hamcrest-core. Please use hamcrest-library if you need more than the core matchers.