Hi Matthias,
The problem was already mentioned by Joern in LBCLASSIC-246 [1].
ConfigurationWatchList mistakenly outputs an error message complaining
about logbac.xml being in a jar file. The message should be of type INFO
instead of ERROR. Otherwise, the config file should be read just fine.
HTH,
--
Ceki
[1] http://jira.qos.ch/browse/LBCLASSIC-246
On 27.01.2011 15:37, Matthias Treydte wrote:
Hello,
I just found that the latest release (0.9.28) fails to find the
logback.xml file on Windows:
C:\temp\mwserv2>java -jar standalone-2.0-alpha-3-SNAPSHOT.jar -Dlog_level=DEBUG
15:09:48,612 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
Could NOT find resource [logback.groovy]
15:09:48,612 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
Could NOT find resource [logback-test.xml]
15:09:48,612 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
Found resource [logback.xml] at
[jar:file:/C:/temp/mwserv2/standalone-2.0-alph
a-3-SNAPSHOT.jar!/logback.xml]
15:09:48,628 |-ERROR in
ch.qos.logback.core.joran.spi.ConfigurationWatchList@fe64b9 - URL
[jar:file:/C:/temp/mwserv2/standalone-2.0-alpha-3-SNAPSHOT.
jar!/logback.xml] is not of type file
15:09:48,691 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - debug
attribute not set
...
It seems to work on Linux, no other systems were tested. This problem
does not occur with logback 0.9.27, so I think this is a regession.
Kind regards,
-Matthias
PS: Thanks for this nice logging framework, and especially slf4j can
be a life-saver! :-)
_______________________________________________
Logback-user mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-user
