[infinispan-issues] [JBoss JIRA] Commented: (ISPN-659) Consider migrate from log4j to slf4j+logback

[Hendy Irawan (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595733#comment-12595733 ] 

Hendy Irawan commented on ISPN-659:
-----------------------------------

I really wonder why everybody kept reinventing the wheel, and inventing a more inferior wheel in that regard.

SLF4J the API is a logging API without any dependency other than itself, it's designed to replace org.infinispan.util.logging.*. The API is excellent, and is very small, just 25 KB.

"the logging framework in Infinispan is pluggable". There needs to be a limit on the abstraction and redirection. Creating an API just to abstract another API has no merit, but there is performance penalty and more complexity.

SLF4J is first, and foremost, a logging **API**, NOT a logging implementation.

SLF4J has pluggable implementations, and supports Log4J, Logback, among others.

> Consider migrate from log4j to slf4j+logback
> --------------------------------------------
>
>                 Key: ISPN-659
>                 URL: https://issues.jboss.org/browse/ISPN-659
>             Project: Infinispan
>          Issue Type: Feature Request
>    Affects Versions: 4.2.0.ALPHA2
>            Reporter: Niktia Koksharov
>            Assignee: Manik Surtani
>
> Please use slf4j module as logging component and logback. The author of log4j went on to write "logback" which is an implementation of slf4j that has much better performance than log4j and much cleaner output.
> Hibernate, EHCache have moved to SLF4j

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira