Issue #139 has been updated by Jonathan Clarke.
R?my-Christophe Schermesser wrote: > Here my idea : > > We use properties for a default logger with a default configuration. > > And if some user wants to change the behavior of the loggers (Csv, > JndiModifications, etc.) he goes and dig in the xml file > > What do you think ? Well, that's the same as current behaviour. But that sucks, because it's a different config file from everything else, and it's obscure... so XML just makes it more obscure. It'll work for a first version though. Is it possible to inject parameters programattically to logback (via something.setConfiguration or addAppender, for example, like in log4j) ? > ps : the migration is almost done for lsc-core Great! Looking forward to trying it :) ---------------------------------------- Feature #139: Migrate from log4j to sfl4j & LogBack http://tools.lsc-project.org/issues/show/139 Author: R?my-Christophe Schermesser Status: New Priority: Low Assigned to: Category: Core Target version: 1.2 branch Log4j is no longer maintained, so we should migrate to the new standard sfl4j (api) and LogBack (implementation) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20091106/da10650b/attachment.htm>
