groovy

Replace use of mockobjects.com with jMock

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.6-beta-1
  • Component/s: mocks and stubs
  • Labels:
    None
  • Number of attachments :
    0

Description

Groovy still depends on the outdated mockobject.com library; it should be replaced by either jMock or EasyMock; probably jMock. Feel free to comment. I first need to learn the mock APIs.

Issue Links

Activity

Hide
David Emmett added a comment -

Hi,

mockobjects.com is now properly broken, as an API change in junit-3.8.2 changed the visibility of a method in Assert from private to public, and mockobjects overrode that method as protected, making mockobjects impossible to compile against junit-3.8.2. For more details, see bug #1629943 at the mockobjects project:

http://sourceforge.net/tracker/index.php?func=detail&aid=1629943&group_id=18189&atid=118189

This means that anyone using the junit 3.8.2 library can't build groovy. This makes getting rid of mockobjects more important. Hopefully, this can be done soon ...

David

Show
David Emmett added a comment - Hi, mockobjects.com is now properly broken, as an API change in junit-3.8.2 changed the visibility of a method in Assert from private to public, and mockobjects overrode that method as protected, making mockobjects impossible to compile against junit-3.8.2. For more details, see bug #1629943 at the mockobjects project: http://sourceforge.net/tracker/index.php?func=detail&aid=1629943&group_id=18189&atid=118189 This means that anyone using the junit 3.8.2 library can't build groovy. This makes getting rid of mockobjects more important. Hopefully, this can be done soon ... David
Hide
Claus Ibsen added a comment -

Could we get this on the roadmap please?

Using Groovy for unit testing is a big plus.

Show
Claus Ibsen added a comment - Could we get this on the roadmap please? Using Groovy for unit testing is a big plus.
Hide
Paul King added a comment -

Regarding the last comment, the mockobjects dependency is only used in some no longer advertised and probably rarely used classes. The remaining work on this issue is just to remove these legacy classes altogether. Mocking support using alternative mechanisms is already built-in without these legacy classes.

Show
Paul King added a comment - Regarding the last comment, the mockobjects dependency is only used in some no longer advertised and probably rarely used classes. The remaining work on this issue is just to remove these legacy classes altogether. Mocking support using alternative mechanisms is already built-in without these legacy classes.
Hide
Paul King added a comment -

javadoc @deprecated tags have been added to 1.6 and 1.5.5

Show
Paul King added a comment - javadoc @deprecated tags have been added to 1.6 and 1.5.5
Hide
Paul King added a comment -

mockObjects removed from trunk

Show
Paul King added a comment - mockObjects removed from trunk

People

Vote (4)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: