[xwiki-devs] SLF4J/@Inject for logging move - Remaining work
Ok I've committer a first version of the move. So what remains to be done: 1) Migrate code to use @Inject Logger logger; instead of using deprecated Logenabled/AbstractLogEnabled 2) Use the new SLF4J solution for performant logging whenever possible: logger.debug("blah {} blah {}", var1, var2) 3) Move all non component code to use SLF4J and not commons logging I need help from everyone to finish this up, over time. Please let me know if you have any question I also have to update the documentation on xwiki.org which I'll do in the coming few days. Thanks -Vincent
A bit off-topic question, Have you used http://www.slf4j.org/migrator.html in your migration? Just wondering how good and helpful it is. Roman -- View this message in context: http://xwiki.475771.n2.nabble.com/SLF4J-Inject-for-logging-move-Remaining-wo... Sent from the XWiki- Dev mailing list archive at Nabble.com.
On May 18, 2011, at 3:10 PM, coldserenity wrote:
A bit off-topic question, Have you used http://www.slf4j.org/migrator.html in your migration? Just wondering how good and helpful it is.
nope haven't used it, sorry... :) -Vincent
On May 12, 2011, at 3:51 PM, Vincent Massol wrote:
Ok I've committer a first version of the move.
So what remains to be done:
1) Migrate code to use @Inject Logger logger; instead of using deprecated Logenabled/AbstractLogEnabled
all done
2) Use the new SLF4J solution for performant logging whenever possible: logger.debug("blah {} blah {}", var1, var2)
not done. this is limited by the fact that SLF4J doesn't support passing params + passing the exception.
3) Move all non component code to use SLF4J and not commons logging
all done Thanks -Vincent
I need help from everyone to finish this up, over time.
Please let me know if you have any question
I also have to update the documentation on xwiki.org which I'll do in the coming few days.
Thanks -Vincent
participants (2)
-
coldserenity -
Vincent Massol