I'd opt in for something like: LiftRules.logger = Log4J
or LiftRule.logger = MyOwnLogger Br's, Marius On Feb 25, 11:23 am, Jeppe Nejsum Madsen <je...@ingolfs.dk> wrote: > Hi, > > I'm about to start sprinkling the new logging code over some of Lift's > internals. But first, the logging backend needs configuring. > > When the dust has settled and the new logging code is fully implemented, > this needs to happen in a client app: > > 1) Choose a logging backend and add the dependency (ie slf4j-log4j or > logback-classic) > 2) Initialize the logging backend > > For step 2) I was thinking of some simple helpers that configures the > logging backend using lift's properties: > > Log4j.configure > Logback.configure > > Very simple, so I don't think there is a need to specify a setup > function in either LogBoot or LiftRules. But opinions wanted! > > The current logging code will be deprecated and until removed, the > following will happen: > > 1) slf4j-log4j will be added as dependency to lift-util > 2) The current LogBoot.loggerSetup will call Log4j.configure > > Thoughts? > > /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
