accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Coleman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3840) Refactor OpTimer so that it does not use log4j logger.
Date Sun, 19 Jul 2015 00:41:04 GMT

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

Ed Coleman updated ACCUMULO-3840:
---------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Changes merged with master (1.8).  Instead of deprecating OpTimer and adding new EventTimer
class, replace OpTimer with new the functionality.  This changes the contract for OpTimer;
OpTimer is not part of the public-api.

Incorporated comments from RB - added throws for IllegalStateException.

Deferring static methods - expect that various Timers and tracing will be evaluated under
separate ticket.

> Refactor OpTimer so that it does not use log4j logger.
> ------------------------------------------------------
>
>                 Key: ACCUMULO-3840
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3840
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 1.6.2, 1.7.0
>            Reporter: Ed Coleman
>            Assignee: Ed Coleman
>            Priority: Minor
>             Fix For: 1.8.0
>
>         Attachments: ACCUMULO-3840-1.patch, ACCUMULO-3840.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> OpTimer currently uses log4j specific classes. OpTimer and the callers can be modified
so that log4j dependencies are not required.
> The evaluation of timer consolidation raised in ACCUMULO-3329 can still be performed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message