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 2012/04/30 09:57:45 UTC
[jira] [Resolved] (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:all-tabpanel ]
Ralph Goers resolved LOG4J2-11.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha1
Assignee: Ralph Goers
The Log4j 1.x bridge provides as much compatibility as possible.
> 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
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> 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.
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