You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org> on 2012/03/14 17:44:40 UTC

[jira] [Updated] (FLUME-301) Upgrade slf4j to 1.6.1 from 1.5.8

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

Arvind Prabhakar updated FLUME-301:
-----------------------------------

    Fix Version/s: v0.9.5
         Assignee:     (was: Bruce Mitchener)
    
> Upgrade slf4j to 1.6.1 from 1.5.8
> ---------------------------------
>
>                 Key: FLUME-301
>                 URL: https://issues.apache.org/jira/browse/FLUME-301
>             Project: Flume
>          Issue Type: Improvement
>            Reporter: Bruce Mitchener
>             Fix For: v0.9.5
>
>
> Before landing my big changes from FLUME-283, I'd like to get an update in place to the current version of slf4j and correct an issue with how it is set up.
> Right now, slf4j is shipping in Flume with slf4j-simple. That means that things using slf4j right now (Thrift and Avro generated code) won't really do much in the way of logging and that logging would be separate from what is currently being done with log4j.
> I'm suggesting in this patch that we get rid of slf4j-simple and switch to slf4j-log4j12 so that things using slf4j log through log4j.
> In Flume-283, I am moving everything from the log4j API over to slf4j and we can revisit at that point which logging API we want to actually be using.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira