How bad is the " isn't 100% backward compatible with JMock 1." In the next release you'll be able to pick which version of JMock to use by setting a single line in build.yml. If we don't make the upgrade yet, you can upgrade for your projects; if we do make the upgrade and it breaks, you can force your projects to use the older version. But generally we don't want to have a point release that breaks, that's better pushed to the next major/minor release.
Assaf On Mon, Sep 22, 2008 at 1:47 PM, Alex Boisvert <[EMAIL PROTECTED]> wrote: > Now self-inflicted: > http://issues.apache.org/jira/browse/BUILDR-150 > > And JMock is now at 2.5.1. > > alex > > > On Mon, Sep 22, 2008 at 1:26 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote: > >> *bump* >> >> On Sat, May 24, 2008 at 8:30 AM, Alex Boisvert <[EMAIL PROTECTED]> >> wrote: >> > (Cross-posting to buildr-user and buildr-dev) >> > >> > While looking into Scala testing, I noticed we're still using JMock 1 >> > (1.2.0) as default. Would anybody oppose upgrading to JMock 2 (2.4.0) by >> > default? >> > >> > JMock 2 features additional and cleaner APIs, but isn't 100% backward >> > compatible with JMock 1. It also requires Java 1.5+. >> > >> > The main reason I'm asking is because ScalaTest and Scala Specs rely on >> > JMock 2. We could override the defaults for Scala projects but I >> figured >> > it would be better to have consistent defaults between Java/Scala. >> > >> > alex >> > >> >
