| Re: [skalli-dev] Switch logging to log4j |
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
Sent: Donnerstag, 25. August 2011 18:55
To: Skalli project developer mailing list
Subject: [skalli-dev] Switch logging to log4j
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
skalli-dev mailing list
skalli-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/skalli-dev
_______________________________________________
skalli-dev mailing list
skalli-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/skalli-dev