tree 6d96bc421827895df23f912aa871739672cf997a
parent d4ceb3f8daf02a39d109921d08f79bf98774e925
author David Ostrovsky <david@ostrovsky.org> 1772185905 +0100
committer Matthias Sohn <matthias.sohn@sap.com> 1772192510 +0100

Bazel: Pin jcl-over-slf4j to SLF4J_VERSION

rules_jvm_external resolved org.slf4j:jcl-over-slf4j to 1.7.36 via
transitive dependencies, while slf4j-api and slf4j-simple are pinned
to 2.0.17.

This resulted in a mixed SLF4J 1.x/2.x setup on the classpath, which
can lead to runtime conflicts.

Add jcl-over-slf4j as an explicit artifact in maven.install to align
the SLF4J bridge with the rest of the logging stack and ensure a
consistent dependency graph.

Test Plan:
  bazel query --output=build @external_deps//:org_slf4j_jcl_over_slf4j

Also pin this artefact to SLF4J_VERSION in the maven build by adding
a corresponding entry under dependencyManagement.

Test Plan:
  $ mvn dependency:tree -Dincludes=org.slf4j:jcl-over-slf4j

Also add this transitive dependency to the target platforms and the
p2 repository.

Change-Id: I1e9e15ac3b2675e624384763dc8c4212a75d656e