Upgrade to SLF4J 1.7.36

2022-02-08 - Release of SLF4J 1.7.36

Correct corrupt "Export-Package" declaration in MANIFEST.MF in log4j-over-slf4j module. This fixes SLF4J-541 reported by Flavio Donzé.

Starting with version 1.7.36, slf4j releases will be reproducible. By reproducible we mean that anyone checking out the code corresponding to the release version from source code repository and building that local copy, will obtain an identical binary to the published binary.

2022-01-25 - Release of SLF4J 1.7.35

• In this release, the "slf4j-log4j12" artifact automatically instructs Maven to use the "slf4j-reload4j" artifact instead. As you might have guessed, the "slf4j-reload4j" binding delegates log processing to the reload4j logging framework.

The reload4j project is a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues. It is intended as a drop-in replacement for log4j version 1.2.17. By drop-in, we mean the replacement of log4j.jar with reload4j.jar in your build with no source code changes in .java files being necessary.

• Fix incorrect version number in the relocation element in slf4j-log4j12/pom.ml. This issue was reported in SLF4J-539 by Alexander Veit.
2022-01-25 - Release of SLF4J 1.7.34

The relocation element in slf4j-log4j12 has incorrect version number. Version 1.7.34 should not be used.