On 30/01/10 3:06 PM, Jeppe Nejsum Madsen wrote:
Indrajit Raychaudhuri<[email protected]> writes:
On 30/01/10 2:47 PM, Jeppe Nejsum Madsen wrote:
David Pollak<[email protected]> writes:
[...]
If you're 100% sure that nothing will break, go for the slf4j-based
approach.
100% certainty is difficult :-)
How about this:
1) Implement new MDC functionality only for Slf4j
+0
2) Switch the default logging to go through Slf4j (with log4j backend), but keep
existing Log4j functionality
+1
3) After a while, cleanup and remove the log4j native logging
-1 deprecate first and then remove later. Given my recent Scala 2.7 to
2.8 porting experience, I now appreciate the significance of
@deprecated() even more :)
You're right of course, but I don't think anybody will ever see the
deprecated warnings since this is Lift internals only (ie users never used
the Log4jLogging trait). But we could deprecate it in step 2)
Quite so. I am possibly going through this paranoia after falling over
couple of times in the past few days.
/Jeppe
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
