Well, the only thing i would like to have would be the appender that already does the zipping of roled over log files. But this can be easily done with a custom appender and I wrote a blog [1] about it how to attach it to karaf, so no real need to actually get it into pax-logging ;)
regards, Achim [1] - http://nierbeck.de/cgi-bin/weblog_basic/index.php?p=201 2011/10/14 Guillaume Nodet <[email protected]> > The main problem I see with logback is that there's no properties based > configuration for logback. > That's a real problem imho because we would not be able to leverage the > OSGi ConfigAdmin which is a key point in order to have a clean interaction > point with all configurations. If you are aware of anything that would > look like a properties based configurator for logback, things may changed. > > That's said, I've still haven't heard any real reasons to swtich to > logback. The version of log4j that is embedded in pax-logging has been > enhanced to fix some over synchronization problem (leading to performance > issues) and also to add the features that were needed (like a split > appender, etc...). > > What need do you have for logback ? > > > On Fri, Oct 14, 2011 at 12:31, samspy <[email protected]> wrote: > >> Is there any ongoing effort for a Logback backend to Karaf? >> >> I can only find rather old messages in this regard. >> >> Thanks, >> Sam >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Running-Karaf-without-PAX-Logging-tp3177504p3421252.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> > > > > -- > ------------------------ > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > -- -- *Achim Nierbeck* Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
