[
http://jira.qos.ch/browse/LBCLASSIC-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11797#action_11797
]
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
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
