I see the value in simple and very straightforward rules for configuration. However, this is seems too restrictive. In my case, I have several components in a test infrastructure that run out of the same classpath but use different logging configurations. Currently, I use the log4j.configuration system property to specify the configuration to use when each component is started. How would I achieve this using logback? anders Sébastien Pennec wrote:
Hello Jens,
Logback uses a configuration policy that follows three steps:
1. Check if a logback.xml file is found. 2. If step 1 fails, check if a logback-test-xml file is found 3. If step 2 fails, auto-configure itself with a basic ConsoleAppender.
-- View this message in context: http://www.nabble.com/Logback-configuration-tf3266547.html#a9417261 Sent from the Logback User mailing list archive at Nabble.com.