[ https://issues.jboss.org/browse/JGRP-1585?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1585 at 3/14/13 2:15 PM: --------------------------------------------------------- Hi David, here are my requirements: # Add vararg log methods to Log [1], e.g. trace(String format, Object... params); # Replace log4j, possible candidates so far: ## log4j2 ## jboss-logging # I currently support JUL and log4j as backends, and these need to be supported. If more backends can be supported, even better # Minimize the number of JARs to be used # No pre-processing phase (mvn or ant) # Ability to change the log level at runtime. This is an issue for me with log4j2, which doesn't support this anymore. It's not enough to be able to periodically reparse the config file, as I want to do this across a cluster, via probe.sh op=UDP.setLevel["trace"] ## Derived from above: extensibility. I might want to extend a logging impl to provide this feature. Or users might ant to provide their own logging frameworks. If you tell me that I need only 1 JAR (plus the backend, but that's up to the deployer), than that sounds appealing. I looked at jboss-logging on GitHub, but am unsure which project I should use there. Do you have documentation on jboss-logging ? I googled, but I think I hit old documentation... [1] https://github.com/belaban/JGroups/tree/master/src/org/jgroups/logging [2] https://github.com/jboss-logging was (Author: belaban): Hi David, here are my requirements: # Add vararg log methods to Log [1], e.g. trace(String format, Object... params); # Replace log4j, possible candidates so far: ## log4j2 ## jboss-logging # I currently support JUL and log4j as backends, and these need to be supported. If more backends can be supported, even better # Minimize the number of JARs to be used # No pre-processing phase (mvn or ant) # Ability to change the log level at runtime. This is an issue for log4j2, which doesn't support this anymore. It's not enough to be able to periodically reparse the config file, as I want to do this across a cluster, via probe.sh op=UDP.setLevel["trace"] If you tell me that I need only 1 JAR (plus the backend, but that's up to the deployer), than that sounds appealing. I looked at jboss-logging on GitHub, but am unsure which project I should use there. Do you have documentation on jboss-logging ? I googled, but I think I hit old documentation... [1] https://github.com/belaban/JGroups/tree/master/src/org/jgroups/logging [2] https://github.com/jboss-logging -- 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