Issue #139 has been updated by Jonathan Clarke.
R?my-Christophe Schermesser wrote: > > Is it possible to inject parameters programattically to logback (via > > something.setConfiguration or addAppender, for example, like in log4j) ? > > Yes, we CAN !! But is it really a good idea ? It will be a lot of code, and > not a very useful feature I was thinking of a simple parameter in LSC properties, that specifies for example: <pre> lsc.tasks.<taskname>.LdifLog = /tmp/updates.ldif </pre> That, when parsed, runs some Java code to add an appender to logback with the filename, using the LDIF layout configured for the appropriate taskName. The idea is to make simple shorthand to avoid copying out the same lengthy configuration used all the time, to the XML file. ---------------------------------------- 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/3cd8fedc/attachment.htm>
