[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
Thu Jul 22 13:11:16 CEST 2010

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

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


More information about the logback-dev mailing list