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

Ceki Gulcu (JIRA) noreply-jira at qos.ch
Wed Jul 21 18:04:16 CEST 2010

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

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


More information about the logback-dev mailing list