[JIRA] Created: (LBCLASSIC-130) Multiple resource warning is not appropriate for logback-test.xml
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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Jon Vincent commented on LBCLASSIC-130: --------------------------------------- Alternatively, if you think the information is too useful to remove (see LBCLASSIC-55), perhaps we could use INFO rather than WARN for logback-test.xml?
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
[ 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu reassigned LBCLASSIC-130: ------------------------------------ Assignee: Ceki Gulcu (was: Logback dev list)
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Joern Huxhorn commented on LBCLASSIC-130: ----------------------------------------- This sounds to me like a bug in Eclipse, not Logback, especially since other IDEs (such as IDEA) don't have such a problem. I'd suggest to report it to the Eclipse community instead of changing Logbacks functionality. Beside that, I think that this issue isn't only a problem because of this Logback warning. It's also quite annoying because it leads to projects that build in Eclipse but won't build on the command line using Maven. The Logback warning is only a symptom of a much bigger problem.
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-130: -------------------------------------- Jon Vincent writes: "Every test in the project will therefore emit this warning when run from the IDE." The warning is emitted when the StaticLoggerBinder class is loaded into memory, which happens once per JVM launch. So, if you are running several tests in a suite, the warning will be emitted only once, at the beginning. Only for tests run individually will the warning will be emitted per test. There inconveniences involved in using INFO instead of WARN: 1) there will still be multiple messages lines output, one per resource plus the initial message about logback-*.xml occuring multiple times. 2) what if the multiple resource occurrence is unintentional. In other words, we lose an opportunity to warn the user about a likely error.
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu edited comment on LBCLASSIC-130 at 7/21/10 12:56 PM: ---------------------------------------------------------------- Jon Vincent writes: "Every test in the project will therefore emit this warning when run from the IDE." The warning is emitted when the StaticLoggerBinder class is loaded into memory, which happens once per JVM launch. So, if you are running several tests in a suite, the warning will be emitted only once, at the beginning. Only for tests run individually will the warning will be emitted per test. There are inconveniences involved in using INFO instead of WARN: 1) multiple messages will still be output, one per resource plus the initial message about logback-*.xml occuring multiple times. 2) what if the multiple resource occurrence is unintentional? In that case, we lose an opportunity to warn the user about a likely error. was (Author: noreply.ceki@qos.ch): Jon Vincent writes: "Every test in the project will therefore emit this warning when run from the IDE." The warning is emitted when the StaticLoggerBinder class is loaded into memory, which happens once per JVM launch. So, if you are running several tests in a suite, the warning will be emitted only once, at the beginning. Only for tests run individually will the warning will be emitted per test. There inconveniences involved in using INFO instead of WARN: 1) there will still be multiple messages lines output, one per resource plus the initial message about logback-*.xml occuring multiple times. 2) what if the multiple resource occurrence is unintentional. In other words, we lose an opportunity to warn the user about a likely error.
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] olivier chaumont commented on LBCLASSIC-130: -------------------------------------------- I agree with Joem, it is better than Eclipse understand the difference between source in src/main and src/test like Maven. I hope the Maven integration will be better in the next Eclipse release. But now we can't change our IDE (more than 50 developpers on multi projects) , and I think it's a good thing that we can define the name of the logback config filename. Why not? Now I can't deploy a web application in Eclipse which is link to other Eclipse project. The logback.xml in web application is never read, and all logback-test.xm in other Eclipse project are loaded. So we have rollback to log4j.
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-130: -------------------------------------- Oliver, By removing all logback-test.xml files in your various modules, you would revert to log4j type behavior with respect to loading configuration files but would still be using logback. Would you agree?
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] olivier chaumont commented on LBCLASSIC-130: -------------------------------------------- Ceki, I agree with you, but I can't remove logback-test.xml in the various modules because if i do that the Junit tests doesn't not produce log.(We need it on Hudson integration build). Log4j load the first log4j.xml file find in the classpath, so on Eclipse it's fine, I can control the console log. On production, Maven build artefact without log4J.xml file, so it's work. We can also use log4j-contrib (http://code.google.com/p/log4j-contrib/) and if the same funtionnality can be had to logBack it would be appreciate. Would you agree?
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-130: -------------------------------------- Olivier Chaumont writes:
Log4j load the first log4j.xml file find in the classpath,
Logback also uses the first resource found on the class path. The only difference is that in addition it *warns* you that there are multiple resources on the class path (but still using the first). Regarding the definition of the logback configuration file name, please see [1] and [2]. As for repository selection [3], logback comes with an equivalent concept. Please see [4]. [1] http://logback.qos.ch/manual/configuration.html#configFileProperty [2] http://logback.qos.ch/manual/configuration.html#joranDirectly [3] http://code.google.com/p/log4j-contrib/ [4] http://logback.qos.ch/manual/loggingSeparation.html
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] olivier chaumont commented on LBCLASSIC-130: -------------------------------------------- You're right, I do a mistake, I re-test it and logBack use the first ressource found on the class path. So i can use a logback-test.xml instead of logback.xml in the web application and it's work. But the specifying the location of the default configuration file as a system property [1] is a good solution for Eclipse. Thank you, we will use logback.
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Holger Hoffstätte commented on LBCLASSIC-130: --------------------------------------------- I understand the reason for the warning when a resource is found multiple times on the classpath, even though I disagree with it; what I don't understand is why the first resource is not picked by default _and used_ - right now it seems that logback ignores them all. Maybe to "not do the wrong thing"? However trying to enforce the config file via system property works only in a trivial number of projects (or run configs) and is error-prone as it pushes additional responsibility of an otherwise correctly set up classpath onto users for no reason. Can we maybe turn the warning off for multiple logback-test.xml files? that seems to fit the intended use case best, for both eclipse and maven.
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-130: -------------------------------------- Holger, But logback does use the first resource found on the list. It just complains that that are multiple resources witht he same name. Add an onConsoleStatusListener [1] to see what logback is doing. In other words just add the following in your config file: <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> In the absence of further input in the next 10 days, I will close this issue. [1] http://logback.qos.ch/manual/configuration.html#statusListener
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.syste... ] Holger Hoffstätte commented on LBCLASSIC-130: --------------------------------------------- Ceki, thanks for looking into this. I just tried to verify the behaviour and you are indeed right: the first config file *is* used correctly after all. Sorry for complaining. :) I guess the additional INFO messages were too confusing - adding the config property "fixed" the problem for me at the time and I didn't look deper into it afterwards. This mattered most to me when running Junit tests in eclipse because I hate spurious Console output that doesn't tell me anything new. However with >50 workspace projects that reference each other and just as many run configurations manually adding the system properties is just very tedious. Maybe logback could use the first config, and only then log the warning but not as INFO but DEBUG. That way the selection process/"warning" would still be visible if the root level is DEBUG, but not annoy in more common cases where I only want to see logging from my custom packages. (I hope that makes sense).
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: Ceki Gulcu 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
participants (5)
-
Ceki Gulcu (JIRA) -
Holger Hoffstätte (JIRA)
-
Joern Huxhorn (JIRA)
-
Jon Vincent (JIRA)
-
olivier chaumont (JIRA)