[ https://jira.jboss.org/browse/ISPN-659?page=com.atlassian.jira.plugin.sys... ] Galder Zamarreño commented on ISPN-659: --------------------------------------- Niktia, the logging framework in Infinispan is pluggable, so you could contribute an impl for slf4j ;) Such impl would best extend org.infinispan.util.logging.AbstractLogImpl. Some extra work would be required to decide which one to chose in LogFactory if both log4j and slf4j are available. A system property could control this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-659?page=com.atlassian.jira.plugin.sys... ] Manik Surtani commented on ISPN-659: ------------------------------------ We really don't need another dependency, esp. on a logging library (which in turn pulls in even more deps) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-659?page=com.atlassian.jira.plugin.sys... ] Galder Zamarreño commented on ISPN-659: --------------------------------------- +1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-659?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-659: --------------------------------------- Hendy, all JBoss projects are standarising on JBoss Logging to provide internationalization, easy i18n...etc, so we'll definitely not using SLF4J. Even Hibernate, which was the only JBoss project that I'm aware of who was using SLF4J has moved to JBoss Logging. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira