Hello all,
I am happy to announce the immediate availability of SLF4J version 1.7.8 which can automatically detect and report mismatches between the class where a logger is defined and the logger name. For more details on this feature see: http://www.slf4j.org/codes.html#loggerNameMismatch The relevant artifacts should hit the Maven central repository within the next few hours. Please refer to the the news page for more details on this release: http://www.slf4j.org/news.html I am grateful to Matt Bishop for managing the SLF4J project in the last few months and in particular for handling the various pull requests submitted on github. This release would not have been possible without his help. The logger name mismatch detection mechanism, an exciting and new feature introduced in this release, was contributed by Alexander Dorokhine. I join the undoubtedly many SLF4J users in thanking Alexander for his great work. The 1.7.x series: The Simple Logging Facade for Java or (SLF4J) serves as a simple facade or abstraction for various logging frameworks, e.g. java.util.logging, log4j and logback, allowing the end user to plug in the desired logging framework at deployment time. The 1.7.x series adds varargs support in Logger methods. Compared to previous versions, 1.7.5 significantly improves logger retrieval times. Users are highly encouraged to migrate to SLF4J 1.7.5 or later. Binary compatibility: Mixing mixing different versions of slf4j-api.jar and SLF4J binding can cause problems. For example, if you are using slf4j-api-1.7.1.jar, then you should also use slf4j-simple-1.7.1.jar, using slf4j-simple-1.5.5.jar will not work. From the client's perspective all versions of slf4j-api are compatible. Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M. You only need to ensure that the version of your binding matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used to compile a given dependency in your project. You can always use *any* version of slf4j-api.jar, and as long as the version of slf4j-api.jar and its binding match, you should be fine. At initialization time, if SLF4J suspects that there may be an api vs. binding version mismatch problem, it will emit a warning about the suspected mismatch. Version 1.7.x series takes compatibility one step further so that slf4j-api and SLF4J bindings can be freely mixed with artifacts from the 1.6.x or 1.7.x series. In other words, when running under JDK 1.5 or later, version 1.7.x is totally 100% no-ifs-or-buts compatible with the 1.6.x series. Downloading SLF4J: You can download SLF4J, including full source code, class files and documentation on our download page: http://www.slf4j.org/download.html Announcement mailing list: You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter: https://twitter.com/qos_ch Enjoy, -- Ceki _______________________________________________ slf4j-user mailing list slf4j-user@qos.ch http://mailman.qos.ch/mailman/listinfo/slf4j-user
