You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2013/10/19 09:31:42 UTC
[jira] [Commented] (ISIS-569) Switch from JMock to something more
modern, eg JMockit
[ https://issues.apache.org/jira/browse/ISIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799821#comment-13799821 ]
Dan Haywood commented on ISIS-569:
----------------------------------
Or the alternative is to work with JMock to get it working with cglib. This is also a blocker for ISIS-568.
> Switch from JMock to something more modern, eg JMockit
> ------------------------------------------------------
>
> Key: ISIS-569
> URL: https://issues.apache.org/jira/browse/ISIS-569
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-2.0.0
>
>
> Isis standardized on using JMock a while back, however as a library it doesn't seem to be keeping up.
> Specifically, its mocking of classes depends on cglib 2.x (and therefore asm 3.x), which conflicts with cglib 3/ asm 4.x (required for JDK 7).
> Candidates to replace it are mockito and jmockit. Personally I don't much like mockito; jmockit comes out well in this comparison:
> https://blog.42.nl/articles/mockito-powermock-vs-jmockit/
--
This message was sent by Atlassian JIRA
(v6.1#6144)