espresso's dependencies pull hamcrest libs separately about android-test-kit HOT 3 CLOSED

I'm having the same problem. It was only occuring when using Junit 3.

As outlined on the wiki, you can also use the separate dependencies to avoid 
this issue. Given that there are workarounds, resolving this bug.

Erm, simply 'WontFix'ing this bug is not sufficient IMHO.

Yes, the wiki describes an alternative path to specifiy dependencies one by one 
by manually copying the libraries into the project, the point of this bug 
however is that the default approach, depending on   the mavencentral 
deployment is problematic, and most people will actually go down that route.

So what could you do about that? Well, either depend in your pom on 
hamcrest-all, like outlined in the bug's description, or _at least_ print a big 
fat warning in your deployment instructions that note that remote dependency 
deployment is otherwise broken.

Thank you!