Thanks Mauro, issue resolved with regards to EnsureThat - I have replaced it by AssertThat! Although I have bumped into new issues which is always good, in the sense gives me more opportunity to learn!
On Sat, Sep 1, 2012 at 2:01 PM, Mauro Talevi <mauro.tal...@aquilonia.org>wrote: > It's been removed. Use Hamcrest MatcherAssert > > > http://code.google.com/p/hamcrest/source/browse/trunk/hamcrest-java/hamcrest-integration/src/main/java/org/hamcrest/MatcherAssert.java?r=287 > > This is independent of JBehave. > > On 01/09/2012 14:59, Mani Sarkar wrote: > > I'm more interested in the ensurethat class that was available with > version 2.5.9 and not available anymore more since 3.0.0. > > Any ideas where it has been moved to? > On 1 Sep 2012 12:44, "Mauro Talevi (JIRA)" <j...@codehaus.org> wrote: > >> Mauro >> Talevi<https://jira.codehaus.org/secure/ViewProfile.jspa?name=maurotalevi>commented >> on [image: >> Task] JBEHAVE-288 <https://jira.codehaus.org/browse/JBEHAVE-288> >> *Replace Ensure methods with Hamcrest direct >> invocations*<https://jira.codehaus.org/browse/JBEHAVE-288> >> >> Hamcrest is just a library that you may or may not use in JBehave. >> You can learn more from its website: http://hamcrest.org/ >> >> Examples of using Hamcrest-based assertion can be found in many places, >> including the JBehave code: https://github.com/jbehave/jbehave-core >> This message is automatically generated by JIRA. >> If you think it was sent incorrectly, please contact your JIRA >> administrators<https://jira.codehaus.org/secure/ContactAdministrators%21default.jspa> >> . >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> --------------------------------------------------------------------- To >> unsubscribe from this list, please visit: >> http://xircles.codehaus.org/manage_email > > >
