[jira] [Resolved] (LOG4J2-5) Appenders, Layouts and other back-end classes should be independent of logging API

["Ralph Goers (JIRA)" <ji...@apache.org>]

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

Ralph Goers resolved LOG4J2-5.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-alpha1
         Assignee: Ralph Goers

Marking as resolved since there have been no comments on my previous update.
                
> Appenders, Layouts and other back-end classes should be independent of logging API
> ----------------------------------------------------------------------------------
>
>                 Key: LOG4J2-5
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-5
>             Project: Log4j 2
>          Issue Type: Wish
>          Components: Appenders
>            Reporter: Curt Arnold
>            Assignee: Ralph Goers
>             Fix For: 2.0-alpha1
>
>
> Appenders and related classes should be able to work on a logging event interface and not be tied to a specific logging API and its native LoggingEvent class.  The logging event interface should be readily implementable as a thin wrapper around established logging events such as o.a.l.spi.LoggingEvent and java.util.logging.LogRecord.  log4j 2.0 appenders should be usable as java.util.logging.Handler's with a simple adapter.

--
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org