[
https://issues.jboss.org/browse/ISPN-659?page=com.atlassian.jira.plugin.s...
]
Hendy Irawan commented on ISPN-659:
-----------------------------------
Thanks Galder.
The original rejection on this issue had a different rationale:
1. prefers the "logging framework in Infinispan"
2. "We really don't need another dependency"
both rationale are false now, that:
1. the internal Infinispan logging framework is being deprecated in favor of JBoss
Logging
2. Infinispan added another (external) dependency anyway: JBoss Logging
I do not object to JBoss Logging at all, I just object to having a layer of logging
framework inside Infinispan itself. And it is being resolved, so I am happy.
My recommendation is, re-mark resolved this issue from "Rejected" to
"Duplicate of ISPN-792".
I do see merits in JBoss Logging when compared to SLF4J. To be honest I would love the
JBoss Logging team to contribute directly and influence the direction of SLF4J (the API,
not implementation) than to create a competing framework. But that is another issue.
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