accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-3162) make log members (to the extent possible) private static final
Date Tue, 23 Sep 2014 14:30:33 GMT

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

Eric Newton resolved ACCUMULO-3162.
-----------------------------------
    Resolution: Fixed

> make log members (to the extent possible) private static final
> --------------------------------------------------------------
>
>                 Key: ACCUMULO-3162
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3162
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client, master, test, tserver
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Trivial
>             Fix For: 1.7.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> While ripping through the fluo code, I tried to make as members final as possible.  A
quick check of the accumulo code finds that we don't even make the log4j log entries consistent
as "private static final".  Some log members are non-private because components still use
them even though they have been refactored into their own files.  Some members are protected
on purpose, and are meant to be re-used by subclasses (especially in tests).
> To the extent possible, make the log4j log members consistent.



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

Mime
View raw message