geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-258) Remove deprecated Cache.getLoggerI18n and getSecurityLoggerI18n methods
Date Wed, 26 Apr 2017 01:07:04 GMT

    [ https://issues.apache.org/jira/browse/GEODE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983949#comment-15983949
] 

ASF GitHub Bot commented on GEODE-258:
--------------------------------------

Github user upthewaterspout commented on the issue:

    https://github.com/apache/geode/pull/467
  
    I'm not quite sure about this one. LogWriter and LoggerI18n are also deprecated. I believe
they were deprecated because geode is now using log4j2.
    
    @dschneider-pivotal  - It looks like this PR contains the changes suggested in the ticket,
but is just removing these two methods really what we want to do?
    
    My other query is that log4j2 was introduced fairly recently, so is it too soon to remove
LogWriter and LogWriterI18n?


> Remove deprecated Cache.getLoggerI18n and getSecurityLoggerI18n methods
> -----------------------------------------------------------------------
>
>                 Key: GEODE-258
>                 URL: https://issues.apache.org/jira/browse/GEODE-258
>             Project: Geode
>          Issue Type: Sub-task
>            Reporter: Darrel Schneider
>            Assignee: Avinash Dongre
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Remove the deprecated Cache.getLoggerI18n and getSecurityLoggerI18n methods. All calls
can be replaced with getLogger().convertToLogWriterI18n() so this should be a quick task.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message