[
https://issues.jboss.org/browse/JBLOGGING-62?page=com.atlassian.jira.plug...
]
Hendy Irawan updated JBLOGGING-62:
----------------------------------
Description:
I do see merits in JBoss Logging when compared to SLF4J.
However 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 API (of which
there are overlap, and JBoss Logging adds some powerful features to the API, like typed
loggers, logger injection, typed message bundles/internationalization and more).
JBoss Logging can still retain its own logging implementation, much like the way Logback
is the implementation of SLF4J API.
My suggestion is that the JBoss should submit API improvements to SLF4J, so that on the
API level it everybody can use the same rich API that JBoss Logging provided in SLF4J.
This would benefit both JBoss and SLF4J communities.
was:
I do see merits in JBoss Logging when compared to SLF4J.
However 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 API (of which
there are overlap, and JBoss Logging adds some powerful features to the API, like
internationalization and more).
JBoss Logging can still retain its own logging implementation, much like the way Logback
is the implementation of SLF4J API.
My suggestion is that the JBoss should submit API improvements to SLF4J, so that on the
API level it everybody can use the same rich API that JBoss Logging provided in SLF4J.
This would benefit both JBoss and SLF4J communities.
Contribute to SLF4J API
-----------------------
Key: JBLOGGING-62
URL:
https://issues.jboss.org/browse/JBLOGGING-62
Project: JBoss Logging
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: jboss-logging-spi
Affects Versions: 3.0.0.Beta4-jboss-logging
Reporter: Hendy Irawan
Assignee: David Lloyd
I do see merits in JBoss Logging when compared to SLF4J.
However 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 API (of which
there are overlap, and JBoss Logging adds some powerful features to the API, like typed
loggers, logger injection, typed message bundles/internationalization and more).
JBoss Logging can still retain its own logging implementation, much like the way Logback
is the implementation of SLF4J API.
My suggestion is that the JBoss should submit API improvements to SLF4J, so that on the
API level it everybody can use the same rich API that JBoss Logging provided in SLF4J.
This would benefit both JBoss and SLF4J communities.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira