accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3920) Deprecate mock and cease using it in our tests
Date Wed, 08 Jul 2015 23:20:04 GMT


Christopher Tubbs commented on ACCUMULO-3920:

Note: there are some places where Mock is still needed in our code, to support various functionality
we've given first-class citizenship to for mock. This is primarily mock-related features in
MapReduce and the shell. For these things, in order to stop using Mock and to avoid propagating
up a bunch of deprecation warnings about its continued usage, I intend to create a non-public-API
class called DeprecationUtil for use in the implementation which must remain. This class will
provide static methods which wrap the existing calls directly to Mock, and will be responsible
for suppressing deprecation warnings so that the non-Mock code which currently depends on
Mock can remain in-tact as much as possible, until Mock is actually removed.

> Deprecate mock and cease using it in our tests
> ----------------------------------------------
>                 Key: ACCUMULO-3920
>                 URL:
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.8.0
> Numerous prior discussions have occurred, expressing a desire to deprecate (deprecate
is not the same as remove) mock, so we can properly communicate its current status as a "dying"
(poorly maintained, not kept up-to-date, lacking features) component of Accumulo. Some interest
has been expressed in keeping it around, but no work has been put in to it to fix it's numerous
divergences from the behavior of "real" Accumulo, add its missing features, or to improve
its API.
> The task here is to:
> * Cease and desist using mock in our tests (replacing it with MAC, EasyMock, etc., as
> * Mark mock {{@Deprecated}} until it is eventually removed in a major release
> Further discussion, if necessary, can be held later regarding its actual removal.

This message was sent by Atlassian JIRA

View raw message