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

Holger Hoffstätte (JIRA) noreply-jira at qos.ch
Wed Oct 20 12:14:51 CEST 2010

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

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


More information about the logback-dev mailing list