If a classpath ends up putting both log4j-over-slf4j (3 lines above) and slf4j-log4j12 on the classpath, that can often give an infinite loop when the first log statement is called. The slf4j docs clearly state they should never be on the same classpath.

This is not a dependency issue, but a logging standardization issue.
I presume that the platform builds now workaround this issue by excluding all but 1 logging mechanism.
I'd ignore this issue for now as we got bigger fish to fry.

But - long term - should we, in the IP BOM, promote multiple logging implementations(slf4jWithLogback and log4j) by defining multiple?