https://issues.apache.org/bugzilla/show_bug.cgi?id=48704
--- Comment #5 from Ceki Gulcu <[email protected]> 2010-02-11 18:03:54 UTC --- * SLF4J ships with a migration tool [1] which significatly eases the pain of migrating to SLF4J from log4j. Once you migrate to SL4J, you can either continue to use log4j or switch to logback. Since logback natively implements the SLF4J API, you don't need change the code in *your* application. BTW, that is the whole point of SLF4J. * Although log4j has been vegetating for several years, I don't see any indication that log4j will be officially retired any time soon. * The logging API of logback is determined by SLF4J which is very stable. However, although logback internals are relatively stable, that stability is not guaranteed and radical changes may occur. More specifically, there are proposals [2] to change the way FileAppender and co. write their output to log files. When this change is adopted, it will affect your implementation of RFA. Nevertheless, you should be able to adapt to the changes with few lines of code on your side. It should be mechanical change... [1] http://www.slf4j.org/migrator.html [2] http://jira.qos.ch/browse/LBCORE-128 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
