I’ve been seeing this ever since we upgraded to 0.9.28, and have
been meaning to open an issue about it. It’s not specific to Groovy based
configuration. It’s really a pain when every unit tests produces this output,
since it makes it much harder to simply grep for ERRORs… You’re correct that
it seems to not like the fact that the config file is jarred up.
From: Evgeny Goldin
[mailto:evgenyg@gmail.com]
Sent: Thursday, March 24, 2011 2:48 PM
To: logback-user@qos.ch
Subject: [logback-user] ERROR: URL
[jar:file:/something.jar!/logback.groovy]is not of type file
Hi,
I get the
following error when my library starts. It uses Logback via SLF4J API and "logback.groovy"
is packed in the root of jar file.
20:36:58,117 |-INFO
in ch.qos.logback.classic.LoggerContext[default] - Found resource
[logback.groovy] at [jar:file:/C:/Users/evgeny/.m2/repository/.../gcommons-0.5.3-SNAPSHOT.jar!/logback.groovy]
20:36:58,122 |-ERROR
in ch.qos.logback.core.joran.spi.ConfigurationWatchList@139d891 - URL
[jar:file:/C:/Users/evgeny/.m2/repository/../gcommons-0.5.3-SNAPSHOT.jar!/logback.groovy]
is not of type file
20:36:58,401 |-INFO
in ch.qos.logback.classic.gaffer.ConfigurationDelegate@b92dc2 - About to
instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
20:36:58,402 |-INFO
in ch.qos.logback.classic.gaffer.ConfigurationDelegate@b92dc2 - Naming appender
as [CONSOLE]
I tracked it
down to ConfigurationWatchList.convertToFile()
that raises this error.
1) Is it a bug
that this an Ok jar-based URL is marked as an error?
2) Can I start
up the library silently without those messages displayed? This is my main goal
here.
Thanks!