Issue #139 has been updated by Jonathan Clarke.
Rémy-Christophe Schermesser wrote: > The first (and I hope the last) issue, is that there is no FATAL level in > sfl4j. > There is a FATAL level but only for backward compatibility for log4j & co. > The new interface does not define one > (http://www.slf4j.org/apidocs/org/slf4j/Logger.html) > > How should we migrate this level ? > > Should we migrate it to a standard ERROR level ? Or do we keep log4j ? As far as I know, there have never been any explicit conventions about log levels in LSC. I agree with SFL4J authors' opinion: FATAL is just an ERROR message that then causes the program to halt. So if there are any FATAL logs in LSC, you can make them ERROR, in my opinion. ---------------------------------------- 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.0 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
_______________________________________________ lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
