| Re: [skalli-dev] Switch logging to log4j |
Hi, good point. And the change is just a find/replace action. I am testing it currently, if all logs appear as they should. CQ is filed. Regards, Robert From: skalli-dev-bounces@xxxxxxxxxxx [mailto:skalli-dev-bounces@xxxxxxxxxxx] On Behalf Of Simon Kaufmann When touching all sources anway, why not switching to slf4j (and then using the log4j binding as a default)? We'd then gain more flexibility and could switch to any other widely used logging library without having to touch the code again. Simon 2011/8/26 Ochmann, Michael <michael.ochmann@xxxxxxx> +1 for switching to log4j The old mechanism with the adapter to the OSGi logging service, even after my refactoring recently, was not reliable enough. Furthermore, neither java.util.logging nor OSGi logging service is in wide spread use, so that most runtimes don’t aggregate logs from that sources well (if at all). Regards, Michael From: skalli-dev-bounces@xxxxxxxxxxx [mailto:skalli-dev-bounces@xxxxxxxxxxx] On Behalf Of Wetzold, Robert Hi, we plan to switch the current java.util.logging to log4j which provides additional functionality and configuration options. This way we also get rid of the o.e.s.log bundle, which is no longer needed then. Are there any objections? I will prepare a patch in the mean time. Regards, Robert
|