Users yet unfamiliar with SLF4J sometimes unknowingly place both log4j-over-slf4j.jar and slf4j-log4j12.jar simultanously on the class path, causing stack overflow errors. Simultaneously placing both jcl-over-slf4j.jar and slf4j-jcl.jar on the class path is another occurrence of the same general problem. As of this version, SLF4J preempts the inevitable stack overflow error by throwing an exception with details about the actual cause of the problem. This is deemed to be better than leaving the user wondering about the reasons of the StackOverflowError.
This version corrects critical bugs. You are highly encouraged to upgrade. The upgrade should pose no problems. Nevertheless, you might still want to refer to the compatibility report for this version.
This release consists of bugfixes only. Moreover,
since the major packaging-related changes in
1.1.0-beta0 seem to work well, this release is
marked as 1.1.0-RC0.
This is a maintenance release, correcting bugs #4 and #5. There has
also been an effort to minimize the file sizes of the various jar files
produced by SLF4J, resulting in jar files approximately 40% smaller than
in version 1.0beta9. Given that the SLF4J API is now deemed stable, this
release is marked as release candidate number 1.
To ease migration to SLF4J from JCL, this release includes a jar file called jcl-over-slf4j-1.0.4.jar. This jar file can be used as a drop-in replacement for JCL version 1.0.4. It implements the public API of JCL using SLF4J underneath. Thus, you can immediately benefit from the advantages of SLF4J without waiting for all the libraries you depend on to migrate to SLF4J first.
