You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2013/08/05 20:12:50 UTC
[jira] [Commented] (OFBIZ-5287) Migrating from Log4j 1.2.17 to
log4j2
[ https://issues.apache.org/jira/browse/OFBIZ-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729742#comment-13729742 ]
Jacques Le Roux commented on OFBIZ-5287:
----------------------------------------
While working on Solr integration OFBIZ-5042, I noticed that slf4j seems unused in OFBiz.
I believe it was introduced with JCR. Since JCR is now only in the jackrabbit20120501 branch, I think we can remove the libs.
If ever we need the facade again (to use another log system) we can always put it back...
> Migrating from Log4j 1.2.17 to log4j2
> -------------------------------------
>
> Key: OFBIZ-5287
> URL: https://issues.apache.org/jira/browse/OFBIZ-5287
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Priority: Minor
>
> Mostly because of the introduction of [LMAX Disruptor library|http://martinfowler.com/articles/lmax.html] in log4j 2, but not only, I want to upgrade log4j to [log4j 2|http://logging.apache.org/log4j/2.x/]
> [The migration does not seem too hard to do| http://logging.apache.org/log4j/2.x/manual/migration.html]. I found only usage of Appender when unloading containers and of course in
> Debug.java; Appender and LoggerRepository classes
> There is also [a easy to install bridge for SLF4J|https://loggapache.org/log4j/2.x/log4j-slf4j-impl/index.html]
> About LMAX Disruptor, [here is a brief introduction|http://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work],
> I discovered the usage of LMAX Disruptor in log4j2 [through this blog entry|http://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html#.UepjvGTfxFo]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira