Code: Fix class conflict between jcl-over-slf4j and commons-logging about jarhc

[smarkwal]

jcl-over-slf4j indeed seems to be a replacement for commons-logging:

jcl-over-slf4j.jar

To ease migration to SLF4J from JCL, SLF4J distributions include the jar file jcl-over-slf4j.jar. This jar file is intended as a drop-in replacement for JCL version 1.1.1. It implements the public API of JCL but using SLF4J underneath, hence the name "JCL over SLF4J."

Our JCL over SLF4J implementation will allow you to migrate to SLF4J gradually, especially if some of the libraries your software depends on continue to use JCL for the foreseeable future. You can immediately enjoy the benefits of SLF4J's reliability and preserve backward compatibility at the same time. Just replace commons-logging.jar with jcl-over-slf4j.jar. Subsequently, the selection of the underlying logging framework will be done by SLF4J instead of JCL but without the class loader headaches plaguing JCL. The underlying logging framework can be any of the frameworks supported by SLF4J. Often times, replacing commons-logging.jar with jcl-over-slf4j.jar will immediately and permanently solve class loader issues related to commons logging.

Source: https://www.slf4j.org/legacy.html#jclOverSLF4J

An open question now is whether there is a problem that it is supposed to replace commons-logging version 1.1.1 while httpclient (and therefore JarHC) has a dependency on version 1.2.

[smarkwal]

Outcome

• The transitive dependency on commons-logging has been excluded.
• There are no more duplicate classes in JarHC.
• There are no binary incompatibilities reported.