You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2011/06/22 12:11:02 UTC

[jira] [Closed] (BUILDR-150) Upgrade to JMock 2.5.1

     [ https://issues.apache.org/jira/browse/BUILDR-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald closed BUILDR-150.
-------------------------------


> Upgrade to JMock 2.5.1
> ----------------------
>
>                 Key: BUILDR-150
>                 URL: https://issues.apache.org/jira/browse/BUILDR-150
>             Project: Buildr
>          Issue Type: Task
>          Components: Test frameworks
>    Affects Versions: 1.3.2
>            Reporter: Alex Boisvert
>            Assignee: Alex Boisvert
>             Fix For: 1.4
>
>         Attachments: BUILDR-150.txt
>
>
> As sent on the buildr-user and buildr-dev mailing lists:
> http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200805.mbox/%3C5582dd3b0805240830l2457cbdcj52d6efc37f1ec74c@mail.gmail.com%3E
> 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?  [Ed. note: JMock 2.5.1 as of September 22nd, 2008]
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira