Using hamcrest 1.1 causes dexing problems about android-test-kit

[GoogleCodeExporter]

This is coming from hamcrest-generator. Hamcrest-generator is a CLI tool which 
generates static factory classes. As such it really shouldn't be going into 
your runtime dependencies - since it's a build time tool.

Our hamcrest dependencies are:
hamcrest-core
hamcrest-integration
hamcrest-library


Thanks for offering the hamcrest 1.3 patch. However - we need to do some 
janitorial work internally (but actually external to espresso) to upgrade from 
1.1 to 1.3. As such we'll need to wait a bit.

Original comment by [email protected] on 5 Nov 2013 at 7:49

[GoogleCodeExporter]

I'm marking this won't fix because it should work if you do not put 
hamcrest-generator in your runtime class path. If you still have issues please 
let me know.

1.1 to 1.3 is a whole different can of worms.

Original comment by [email protected] on 5 Nov 2013 at 7:51

• Changed state: WontFix