This fixes bug 79 reported by Mathias Bogaert. This release consists of bug fixes. Given that the same package name in different modules is a showstopper in Java 9, the org. Moreover, since the major packaging related changes in 1. The add method in BasicMarker class now correctly prevents multiple addition of the same child. Given the practical significance of this change, we highly recommend that library-authors upgrade to version 1. Added setThreshold method in AppenderSkeleton class in the log4j-over-slf4j module. 
| Uploader: | Negul |
| Date Added: | 13 May 2015 |
| File Size: | 37.94 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 66468 |
| Price: | Free* [*Free Regsitration Required] |
See the relevant FAQ entry for further details. Launch of the SLF4J project. This release adds support jck-over-slf4j-1.6.4 the Marker interface. In previous releases the reference was set at the beginning and re-used.
LoggerFactory class is now packaged within the slf4j-api. Addition of the getMDCAdapter method to jcl-over-slfj-1.6.4. Given the practical significance of this change, we highly recommend that library-authors upgrade to version 1.
The printing methods in org. The log4j binding will now alert the user if she uses SLF4J with a version of log4j earlier than 1. Fixed bug 65 reported by Ben Gidley.
Maven Repository: 4j » jcl-over-slf4j »
Initialization of the slf4j-log4j12 module is now thread safe fixing SLF4J LoggerWrapper in the slf4j-ext module now correctly deals with markers. The manifest file for jclover-slf4j now jcl-voer-slf4j-1.6.4 declares version 1.
MF for the slf4j-log4j12 module. Following Eric's suggestion, jclover-slf4j now includes the aforementioned classes.
Thus, instead of throwing an exception, SLF4J will emit a single warning message about the absence of a binding and proceed to discard all log requests jcl-over-slf4j-1.64 further protest. MF files now include OSGi metadata. As of SLF4J version 1.
This improvement was contributed by Vivek Pathak in a pull request.
Index of /repositories/releases/org/slf4j/jcl-over-slf4j/1.6.4
Instead, SLF4J now creates substitute loggers which delegate to the appropriate logger implementation after jcl-overslf4j-1.6.4 initilization phase completes. Moreover, these changes have no incidence on the published interface of SLF4J. SLF4J requires log4j 1. In other words starting with slf4j 1. This fixes bug reported by Laurent Pellegrino with Piotr Jagielski providing the appropriate patch.
Download jcl-over-slf4j-1.6.6.jar : jcl « j « Jar File Download
Added the assertLog boolean, String method in the Category class, in module log4j-over-slf4j. Many thanks to Christian Beil for accurately reporting bug 4. It is now possible to obtain the root logger of the underlying logging implementation by requesting a logger named "ROOT". Removed unnecessary export of org.
Download jcl-over-slf4j JAR ➔ With all dependencies!
Interestingly enough, this bug was picked up by new unit tests and has not been reported as a bug by our users. The resulting internal changes are detailed in the FAQ page.
If the argument array passed to a Logger printing method debug, info, etc. MDCloseable instead of the more generic java. Updated log4j dependency to version 1. More importantly, the log4j-over-slf4j module has been moved to the logback project, under the name log4j-bridge.
Fixed LoggerFactory initialisation problem in presence of SecurityManager denying "createSecurityManager" runtime permission.
Комментарии
Отправить комментарий