[ http://jira.qos.ch/browse/LBCORE-157?page=com.atlassian.jira.plugin.system.i... ] Ceki Gulcu commented on LBCORE-157: ----------------------------------- Hello Andres, The "encoding" property has to be part of the encoder and is now called "charset". Remove the <encoding> element and insert a <charset> element as a child of the <encoder>. HTH,
Initial log messages have changed after 0.9.19 version ------------------------------------------------------
Key: LBCORE-157 URL: http://jira.qos.ch/browse/LBCORE-157 Project: logback-core Issue Type: Bug Components: Joran Affects Versions: 0.9.19 Reporter: Andres Gomez Casanova Assignee: Logback dev list
Sorry, I posted this message in SLF4J, and it is probably better here. I'm developing an application for command line, and I use slf4j + logback for logging (http://db2sa.sourceforge.net/) When using normally (not testing, not debugging), I have to show less messages in the screen, so the logging has not to be verbose. Just the important messages has to be shown. I was using the version 0.9.15, and I updated my application to the version 0.9.21. I saw, that the layout has to be changed to encoder, and I did it in the xml configuration file. However, I'm facing a problem when starting the application. The logger is showing all the configuration phase, and I'm sure that the internal log is not in debug: <configuration debug="false"> It seems that the new version does not take in account this property. I searched the problematic version, and this issue was introduced in the version 0.9.19. I created an example for showing the difference when loading the configuration between 0.9.18 and 0.9.19. It can be executed by running the .bat
-- 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