Hi devs, After progressing on the new logging implementation I've come to the conclusion that we don't need our own facade in xwiki-commons-logging. I started doing the facade and then hit the issue that we need a facade for the MDC feature too (Mapped Diagnostic Context) so that would be one more class to add. If you follow in the direction what will happen is that we will, in the end, completely copy the slf4j-api sources, just under a different name. So my proposal is that we standardize on the SLF4J API and use it directly without any facade. The rationale is: * The SLF4J API is in a single jar (slf4j-api.jar) which is a minimal JAR weighting 23KB (small) * The SLF4J API can be implemented over all existing logging systems. There are currently implementation for at least log4j, jdk14 logging, commons logging, logback and more. So it's ensured that if we wanted we would be able to write our own implementation of it for whatever log system that can come up. * That's one more thing that we don't have to maintain * It's very mature since the guy who wrote it (Ceki) has gone through the log4j experience Here's my +1

Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, After progressing on the new logging implementation I've come to the conclusion that we don't need our own facade in xwiki-commons-logging. I started doing the facade and then hit the issue that we need a facade for the MDC feature too (Mapped Diagnostic Context) so that would be one more class to add. If you follow in the direction what will happen is that we will, in the end, completely copy the slf4j-api sources, just under a different name. So my proposal is that we standardize on the SLF4J API and use it directly without any facade. The rationale is: * The SLF4J API is in a single jar (slf4j-api.jar) which is a minimal JAR weighting 23KB (small) * The SLF4J API can be implemented over all existing logging systems. There are currently implementation for at least log4j, jdk14 logging, commons logging, logback and more. So it's ensured that if we wanted we would be able to write our own implementation of it for whatever log system that can come up. * That's one more thing that we don't have to maintain * It's very mature since the guy who wrote it (Ceki) has gone through the log4j experience Here's my +1 Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, After progressing on the new logging implementation I've come to the conclusion that we don't need our own facade in xwiki-commons-logging. I started doing the facade and then hit the issue that we need a facade for the MDC feature too (Mapped Diagnostic Context) so that would be one more class to add. If you follow in the direction what will happen is that we will, in the end, completely copy the slf4j-api sources, just under a different name. So my proposal is that we standardize on the SLF4J API and use it directly without any facade. The rationale is: * The SLF4J API is in a single jar (slf4j-api.jar) which is a minimal JAR weighting 23KB (small) * The SLF4J API can be implemented over all existing logging systems. There are currently implementation for at least log4j, jdk14 logging, commons logging, logback and more. So it's ensured that if we wanted we would be able to write our own implementation of it for whatever log system that can come up. * That's one more thing that we don't have to maintain * It's very mature since the guy who wrote it (Ceki) has gone through the log4j experience Here's my +1 Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs