[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] olivier chaumont commented on LBCLASSIC-130: -------------------------------------------- The load of logback-test.xml would be the default configuration, but perhaps we can define the name of the configuration file we want to load in the web application. We can use the web.xml to define the name of the logback config file which is loaded at the start of the web application. I think this request is not minor, because it is very annoying to use logback with multi-module in Eclipse.
Multiple resource warning is not appropriate for logback-test.xml -----------------------------------------------------------------
Key: LBCLASSIC-130 URL: http://jira.qos.ch/browse/LBCLASSIC-130 Project: logback-classic Issue Type: Improvement Affects Versions: 0.9.14, 0.9.15, 0.9.16 Reporter: Jon Vincent Assignee: Logback dev list Priority: Minor
When LBCLASSIC-85 was fixed, it also applied to logback-test.xml. Unfortunately, some IDEs (such as Eclipse) include the test classpath for all modules in a multi-module project -- which means that it's nearly impossible to avoid having multiple logback-test.xml files on the classpath if one project depends on another when running tests in Eclipse. Every test in the project will therefore emit this warning when run from the IDE. Is it possible to have the ContextInitializer only emit this warning for logback.xml, and not logback-test.xml? This would avoid a spurious/unactionable warning for developers using Eclipse.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira