29-Aug-2017
NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the
FAQ for more details.
Last week I wrote about
writing JUnit tests with accurate exception matching. That relies on the
Hamcrest library to work. Unfortunately the
JUnit Maven artefact uses only the
hamcrest-core dependency which leads to some compilation errors like this...
The
dependency tree from
Maven shows up like this...
As expected, but incomplete. After checking the
Hamcrest Distributables page it becomes clear that the
hamcrest-core is the bare minimum dependency and doesn't include the required matchers and supporting classes. What's required is the
hamcrest-library dependency. This is easily resolved, just add this to your
pom.xml file...
The dependency tree now looks like this and all of the compilation errors are fixed!
-i
A quick disclaimer...
Although I put in a great effort into researching all the topics I cover, mistakes can happen.
If you spot something out of place, please do let me know.
All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle).
Use of any information contained in this blog post/article is subject to
this disclaimer.
Igor Kromin
Other posts you may like...