[
https://issues.jboss.org/browse/LOGMGR-80?page=com.atlassian.jira.plugin....
]
Kyle Lape commented on LOGMGR-80:
---------------------------------
Another possibility might be to parse a deployment's {{logback.xml}} (assuming logback
isn't present in a deployment) and try to create an equivalent logging config using
JBoss LogManager, though this very well may be more difficult than providing a modified
logback library.
Support Logback similar to how Log4J is supported
-------------------------------------------------
Key: LOGMGR-80
URL:
https://issues.jboss.org/browse/LOGMGR-80
Project: JBoss Log Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Kyle Lape
Assignee: David Lloyd
It would be nice to have support for Logback similar to how we support Log4J.
Specifically, provide a modified version of Logback with customizations that account for
the classloading behavior of Wildfly/JBoss Modules, thus removing the need to include
logback libraries in deployments.
It could be argued that there is no need for this because Logback does not provide a
logging facade API and that anyone that migrates to Wildfly should migrate their
{{logback.xml}} to something JBoss already supports. While that's a valid point, any
help that could be provided to folks migrating to Wildfly would be appreciated.
--
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