bugfix: exclude transitive logback dependencies

A logback slf4j binding is being pulled in via zookeeper causing issues at runtime because we have two slf4j bindings available. Slf4j chooses one implementation and it can pick logback, which is unexpected. Fixes linkedin#2174 Signed-off-by: Robert Young <[email protected]>
robobario · Jul 23, 2024 · 6b862d1 · 6b862d1
1 parent f23332a
commit 6b862d1
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/build.gradle b/build.gradle
@@ -169,6 +169,7 @@ project(':cruise-control-core') {
     configurations.all {
       exclude group: 'org.slf4j', module: 'slf4j-log4j12'
       exclude group: 'log4j', module: 'log4j'
+      exclude group: 'ch.qos.logback'
     }
     implementation "org.slf4j:slf4j-api:1.7.36"
     implementation "org.apache.logging.log4j:log4j-slf4j-impl:2.17.2"
@@ -267,6 +268,7 @@ project(':cruise-control') {
     configurations.all {
       exclude group: 'org.slf4j', module: 'slf4j-log4j12'
       exclude group: 'log4j', module: 'log4j'
+      exclude group: 'ch.qos.logback'
     }
 
     api project(':cruise-control-metrics-reporter')
@@ -437,6 +439,7 @@ project(':cruise-control-metrics-reporter') {
     configurations.all {
       exclude group: 'org.slf4j', module: 'slf4j-log4j12'
       exclude group: 'log4j', module: 'log4j'
+      exclude group: 'ch.qos.logback'
     }
 
     implementation "org.slf4j:slf4j-api:1.7.36"