aw <[email protected]> writes: > I just upgraded my code to M3 and also replaced my LOGGERs with the > new Loggable trait. I am using LogBack (not Log4j). > > I thought that with 2.0-M3, the following call would be deprecated and > no longer necessary: Slf4jLogBoot.enable()
Yeah, the current situation is less than ideal for people not using the Log4j backend. This was a choice made to ease the life's of people using the default setup. I didn't want to change the existing logging code for backwards compatibility reasons. But I should be able to always make it go through slf4j without any breaking changes. > Alas, I discovered that it is still mandatory, otherwise I get a > NoClassDefFound exception for org.apache.log4j.Priority. I thought > SLF4J was enabled already, so I don't know why I need to explicitly > enable it. Yes, the internal lift logging is still using the "old" logger. It will be cleaned up over time..... > > Secondly, if you read the Wiki: > http://wiki.github.com/dpp/liftweb/logging-in-liftIt says to exclude > org.slf4j:slf4j-log4j12 from lift-mapper. > But I noticed that it is lift-webkit that has the dependency > (transitively from net.liftweb:lift-util) that needs to be excluded. > As a result, I have this instead: > > <dependency> > <groupId>net.liftweb</groupId> > <artifactId>lift-webkit</artifactId> > <version>2.0-M3</version> > <exclusions> > <exclusion> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-log4j12</artifactId> > </exclusion> > </exclusions> > </dependency> > > I recommend updating the wiki entry. It's a community wiki, please update if you find something inconsistent. /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.
