The JUnit team (by freezing an older version of hamcrest into their JAR) are killing it.

24 views
Skip to first unread message

Paul Hammant

unread,
Aug 25, 2011, 7:42:10 AM8/25/11
to Hamcrest Java Users
OR has anyone managed to get a way to overcome this?

I feel driven to fest-asserts.

- Paul

dball9

unread,
Aug 26, 2011, 4:14:46 AM8/26/11
to Hamcrest Java Users
Hi Paul,

I import the newest hamcrest library besides junit, so that I can use
the newest version and all it's features.

Thanks for the reference to fest-asserts, having fluent reflections
and the advantages listed at http://docs.codehaus.org/display/FEST/Comparing+to+Hamcrest
sounds good. But it seems to me that easy extensions with your own
matchers is not possible in fest-asserts. Right?

David

Steve Freeman

unread,
Aug 26, 2011, 4:22:18 AM8/26/11
to hamcre...@googlegroups.com
It's very easy. Use the junit-dep jar (which actually means junit /without/ dependencies). That doesn't include hamcrest and there's no clash.

S.

> --
> You received this message because you are subscribed to the Google Groups "Hamcrest Java Users" group.
> To post to this group, send email to hamcre...@googlegroups.com.
> To unsubscribe from this group, send email to hamcrest-jav...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/hamcrest-java?hl=en.
>
>

Steve Freeman

Winner of the Agile Alliance Gordon Pask award 2006
Book: http://www.growing-object-oriented-software.com

+44 797 179 4105
Twitter: @sf105
Higher Order Logic Limited
Registered office. 2 Church Street, Burnham, Bucks, SL1 7HZ.
Company registered in England & Wales. Number 7522677

Paul Hammant

unread,
Aug 26, 2011, 5:46:26 AM8/26/11
to hamcre...@googlegroups.com
Thanks Steve, but there is a issue with the 4.9 release; the 4.8 release was fine. See pic: http://screencast.com/t/NLZ1r9rTAX9

Dave Saff ack'd this yesterday on Twitter :)

- Paul

Steve Freeman

unread,
Aug 26, 2011, 6:21:22 AM8/26/11
to hamcre...@googlegroups.com
OK. Probably time to ask them to pull it out now. You can just use our MatcherAssert.assertThat anyway.

S

Reply all
Reply to author
Forward
0 new messages