You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2008/06/22 23:57:45 UTC

[jira] Commented: (LOG4J2-11) log4j 2.0 should provide a log4j 1.2 emulation that is reasonably binary compatible with client applications

    [ https://issues.apache.org/jira/browse/LOG4J2-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607121#action_12607121 ] 

Ralph Goers commented on LOG4J2-11:
-----------------------------------

Classes marked as deprecated, such as Category, should be removed.

> log4j 2.0 should provide a log4j 1.2 emulation that is reasonably binary compatible with client applications
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-11
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-11
>             Project: Log4j 2
>          Issue Type: Wish
>          Components: API
>            Reporter: Curt Arnold
>
> log4j 1.2 exposes a substantial amount of its implementation details, but it should be possible to provide an emulation of frequently used log4j 1.2 API classes that could be used as a drop in replacement for log4j 1.2.  This would be similar in scope to the log4j-over-slf4j component provided by slf4j.org.  This shim or adapter would have to be an optional component and would have to have sufficient disclaimers to inform the user that it has known incompatibilities and limitations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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