Hamcrest matchers should be supported by selection and rejection utilities

[GoogleCodeExporter]

Hamcrest matchers provide:
* describeTo and describeMismatch so that very helpful logging can be done 
(especially when composing matchers)
* a plethora of implementations and extensions
* re-use by junit, Jmock and other libraries, so I can write one 
implementation only.

and it's also developed at google!

Please add methods with hamcrest signatures in so that I can stop doing my 
own wrapping etc.

The hamcrest jar would not even be required at runtime, as hamcrest classes 
will only be loaded if those specific methods are used.

(Although I'd love to see predicate -> an extension of matcher -> 
deprecation -> deletion)

Original issue reported on code.google.com by stephen....@gmail.com on 8 Jan 2009 at 2:52

[GoogleCodeExporter]

Thanks for the suggestion.

While Hamcrest is very useful library, I'd rather not add a Hamcrest dependency 
to
the Google Collections build. Google Collections currently has no outside
dependencies (besides the to-be-released unit tests), and I'd like to keep it 
that way.

Original comment by jared.l....@gmail.com on 8 Jan 2009 at 3:23

• Changed state: WontFix