[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-124: -------------------------------------- The JBoss Log Manager extends J.U.L. The reason for the change being large is it's not just a simple "add a Marker and an argument to one method". There are several methods that would need to be added. Then comes updating the slf4j bindings. Then deciding in if we need/want to support it in the jboss-logging facade. It's not just as simple as just adding an API for a marker. There is a JIRA, LOGMGR-30, to add support for compression. Creating a simple zip when a file is rotated would be easy enough. Adding support for other compression algorithms would require a third-party library which might not be the end of the world. We only have a single optional dependency now so in some ways I'm a bit hesitant, but I'm starting to care less :) If you feel this is something that needs to be or should be a priority just let me know. It probably wouldn't be that difficult. Especially if we just want {{.zip}} support. Marker support I'm honestly on the fence about. It would require quite a bit of work for something that, maybe a little more clumsy, but is achievable with standard filters. As far replacing the log manager in WildFly that would be a huge change. We'd have to completely rewrite the logging subsystem. If you want to exclude the logging subsystem you should be able to use logback or log4j/log4j2 in a standalone server. It will not work on domain mode though as there are some dependencies on jboss-logmanager. -- This message was sent by Atlassian JIRA (v6.4.11#64026)