[logback-dev] [JIRA] Commented: (LBCLASSIC-130) Multiple resource warning is not appropriate for logback-test.xml

olivier chaumont (JIRA) noreply-jira at qos.ch
Wed Jul 21 15:29:16 CEST 2010

    [ http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11798#action_11798 ] 

olivier chaumont commented on LBCLASSIC-130:


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


More information about the logback-dev mailing list