Felix Logback currently supports configuring via logback.xml config file and if logging needs to be changed then that file would need to be modified. Compared to that Sling Commons Logback  support some more features and enables configuring appenders via OSGi config and has a good Web Console integration.
> if it makes sense to try and converge the two > modules into a single one, presumably in Apache Felix, as it does not > depend on Sling and can get more community exposure. +1 Implementation wise Commons Log does not depend on any Sling feature (except using sling.home to configure base log directory). So it makes sense to converge the two Chetan Mehrotra  http://sling.apache.org/documentation/development/logging.html On Tue, Jul 10, 2018 at 7:59 PM, Karl Pauls <karlpa...@gmail.com> wrote: > I was thinking about that too - it might make some sense to look into > the log.extension as well as we might be able to package logback with > the launchpad.base and have logging via logback even at framework > start-up this way. > > That said, I don't know enough about our current logging features to > say if this is enough to replace what we have. Certainly would be nice > to remove the circular dependencies we currently have in the logging. > > regards, > > Karl > On Tue, Jul 10, 2018 at 3:42 PM Robert Munteanu <romb...@apache.org> wrote: >> >> Hi, >> >> I noticed that a logback module was recently released in the Felix >> project . >> >> At a glance it seems to have the same high-level objectives as our own >> commons-log implementation, but lacks a number of feature we've built. >> >> Since I'm not that familiar with the codebase, I would like to ask if >> the goals are similar and if it makes sense to try and converge the two >> modules into a single one, presumably in Apache Felix, as it does not >> depend on Sling and can get more community exposure. >> >> Thanks, >> >> Robert >> >> : http://felix.apache.org/documentation/subprojects/apache-felix-log >> back.html > > > > -- > Karl Pauls > karlpa...@gmail.com