Issue #139 has been updated by Jonathan Clarke.

R?my-Christophe Schermesser wrote:
> LogBack is not configurable with properties files, only xml files.

*sigh*
What is with XML configuration files?

> So I don't know if we accept this (big) change. What do you think ?
> 
> There is an online service which takes a log4j property file and translate it 
> into LogBack XML file (http://logback.qos.ch/translator/)

Well, we already have some XML configuration files for iBatis (db2ldap syncs). 
All that matters to me is that configuring LSC is simple. Writing an XML file 
is not simple, however, editing a well commented XML file can be...

But maybe we can configure logging with our own properties, and inject the 
appropriate values into the XML file on launch? If I recall correctly we 
already load lsc.properties before initializing the logger, in 
org.lsc.Launcher, no?
----------------------------------------
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/bcbcda45/attachment.htm>

Reply via email to