config xml in jar file cannot be watched

[benno-mueller-saxess]

The example from https://docs.spring.io/spring-boot/how-to/logging.html does not work because the defaults.xml is in a jar (jar:file:/path/to/.m2/repository/org/springframework/boot/spring-boot/3.4.2/spring-boot-3.4.2.jar!/org/springframework/boot/logging/logback/defaults.xml). It outputs:

ConfigurationWatchList(mainURL=file:/path/to/apache-tomcat-10/webapps/portal-war/WEB-INF/classes/logback-spring.xml, fileWatchList={/path/to/apache-tomcat-10/webapps/portal-war/WEB-INF/classes/logback-spring.xml, /path/to/apache-tomcat-10/webapps/portal-war/WEB-INF/classes/logback/file-appender.xml}, urlWatchList=[}) - Cannot watch [jar:file:/path/to/apache-tomcat-10/webapps/portal-war/WEB-INF/lib/spring-boot-3.4.2.jar!/org/springframework/boot/logging/logback/defaults.xml] as its protocol is not one of file, http or https.

Tested with Logback Version 1.5.16 and 1.5.18

It was changed in commit a496a04 - see ch.qos.logback.core.joran.spi.ConfigurationWatchList#addToWatchList(URL)
(Changed in version 1.5.9)

Please add the support for XML-Config-Files in jar files as before this commit.

[ceki]

@benno-mueller-saxess Thank you for your report.

As far as I understand, it makes no sense to watch for changes in jar files as they are certain to not change during the lifetime of the application (at least not without stop/start). Thus, I fail to see the problem. Can you please expand on your remarks?

[benno-mueller-saxess]

@ceki Thanks for your quick response.

Maybe I missunderstood something. As I understand, the file is used, but not watched. Is this correct?
If this is true, the message is missleading, because it is nothing bad. Logging a message for this provides the user no useful information for a file in a jar file. It confuses the user instead. Surely you can optimize this.