From previous experience I would suggest switching to assertj. It’s not pulled in by as many things so you are less likely to get wierd dependency conflicts and it provides useful output when things don’t match.
Also it’s a fluent api so easy to discover the various matcher methods. Really worth having a look at IMHO Sent from my iPhone > On 28 Sep 2019, at 13:51, Vladimir Sitnikov <sitnikov.vladi...@gmail.com> > wrote: > > I was a bit puzzled with java-hamcrest as well. > > It looks like we should exclude it: (see > https://github.com/hamcrest/JavaHamcrest/issues/183#issuecomment-441154016 > and > http://hamcrest.org/JavaHamcrest/distributables#upgrading-from-hamcrest-1x ) > > Felix, would you please check if adding org.hamcrest:hamcrest:2.1 > and org.hamcrest:hamcrest-library:2.1 solves the problem? > > Vladimir
