object
LoggingAutoConfigurer
Value Members
-
final
def
!=(arg0: AnyRef): Boolean
-
final
def
!=(arg0: Any): Boolean
-
final
def
##(): Int
-
final
def
==(arg0: AnyRef): Boolean
-
final
def
==(arg0: Any): Boolean
-
def
apply(): () ⇒ Unit
-
final
def
asInstanceOf[T0]: T0
-
def
clone(): AnyRef
-
final
def
eq(arg0: AnyRef): Boolean
-
def
equals(arg0: Any): Boolean
-
def
finalize(): Unit
-
final
def
getClass(): Class[_]
-
def
hashCode(): Int
-
final
def
isInstanceOf[T0]: Boolean
-
final
def
ne(arg0: AnyRef): Boolean
-
final
def
notify(): Unit
-
final
def
notifyAll(): Unit
-
final
def
synchronized[T0](arg0: ⇒ T0): T0
-
def
toString(): String
-
final
def
wait(): Unit
-
final
def
wait(arg0: Long, arg1: Int): Unit
-
final
def
wait(arg0: Long): Unit
Function object that can be used in Logger.setup
Tries to determine which logging backend is available and configures it by using either defaults or a mode-dependent configuration file.
To provide your own configuration, add either a log4j.props file or log4j.xml file to your classpath. If using logback, name it logback.xml
If you want to provide a configuration file for a subset of your application or for a specific environment, Lift expects configuration files to be named in a manner relating to the context in which they are being used. The standard name format is:
with hostName and userName being optional, and modeName being one of 'test', 'staging', 'production', 'pilot', 'profile', or 'default. Thus, if you name your log4j config file 'default.log4j.xml' or 'default.log4j.props' it will be picked up correctly.