I got this working last night by putting logback.xml in the root of the jar. My assumption was that the application jar and everything in it was in the classpath.
I do like this method of configuration though - it is a much needed improvement over log4j :) Chris On Tue, Aug 12, 2008 at 2:58 AM, Ceki Gulcu <[EMAIL PROTECTED]> wrote: > > > Hello Chris, > > Try the following adding the following two lines, anytime after logback is > initialized, i.e after you retrieve a logger for the first time. > > LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); > StatusPrinter.print(lc); > > Please let us know how it goes, > > Chris Cheshire wrote: >> I am trying to convert from log4j to logback, and up until now I have just >> used the default logging configuration logback provides. >> >> Now I am trying to get the errors emailing out, and I have created a >> logback.xml, put it under "resources" and compiled it into my application >> jar, yet when I run my app it doesn't appear that the config file is even >> being loaded (I put a debug="true" in the configuration element and nothing >> appears on the console like in the example 3.4 in the documentation). >> >> What am I missing? The documentation says to create a file called >> logback.xml and place it in a folder on the classpath and the default >> configurator will find it, yet it is not. >> >> Please help! >> >> Chris > > -- > Ceki Gülcü > > _______________________________________________ > Logback-user mailing list > [email protected] > http://qos.ch/mailman/listinfo/logback-user > _______________________________________________ Logback-user mailing list [email protected] http://qos.ch/mailman/listinfo/logback-user
