[ https://issues.apache.org/jira/browse/LOG4J2-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers closed LOG4J2-27. ----------------------------- Closing since there have been no further updates. > log4j 2 should implement the SLF4J API directly > ----------------------------------------------- > > Key: LOG4J2-27 > URL: https://issues.apache.org/jira/browse/LOG4J2-27 > Project: Log4j 2 > Issue Type: Wish > Components: API > Reporter: Curt Arnold > Assignee: Ralph Goers > Fix For: 2.0-alpha1 > > Attachments: jspwiki-log.pdf > > > A PDF version of jspwiki-log.odf will be attached to this bug. > On Dec 3, 2008, at 5:41 AM, Ceki Gulcu wrote on log4j-dev: > Hello, > As you are probably aware, more and more projects are adopting the > SLF4J API. I would venture say that SLF4J's adoption rate is roughly > equivalent to that of log4j itself. Although the SLF4J API is not > perfect, most SLF4J users seem to be extremely happy with it. > Harry Metske synthesized various logging paths in JSPWiki > https://issues.apache.org/jira/secure/attachment/12394188/jspwiki-log.odp > I was taken aback by the picture he paints. I think we as log4j > committers owe it to Java developers to propose a saner logging model. > Given the multiplicity of logging APIs in the Java world, I propose > that log4j implement the SLF4J API directly. This can be done in the > next version of log4j, say 1.3 or 2.0. > Unfortunately, the adoption of the SLF4J API by log4j will be break > 100% compatibility with existing log4j clients. More precisely, > logging statements passing java.lang.Object as the message parameter > will need to be changed to java.lang.String. Assuming that the > proportion of logging statements using objects instead string is > extremely small, comparatively few users will be affected. More > importantly, in my experience, even very large projects can be > migrated to the SLF4J API within half an hour. > There is even a tool called slf4j-migrator to help with such > migration [1]. > Is there support for my proposal? > [1] http://www.slf4j.org/migrator.html -- 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-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org