Hi all, You know the ethics of release better than I do.
Is it OK to deprecate classes, if I don't actually remove them prior to 2.0? I would like to move all the Matchers into an org.jbehave.core.matchers package as Michael suggested, but I want to maintain backwards compatibility. I also need to do this if I want to move CustomMatcher into its own class but still maintain compatibility with UsingMatchers.CustomMatcher . Cheers, Liz. PS: UsingMatchers is going to be very much smaller too. PPS: UsingMatchers will still be non-static, but all submatchers will be static. This should allow 1.5ers to statically import matchers, while also allowing people to eg: override eq(...) to include Hibernate deproxifying. -- Elizabeth Keogh [EMAIL PROTECTED] http://sirenian.livejournal.com http://jbehave.org
