From ee643c2114246536551b8b121bbd4ed457127963 Mon Sep 17 00:00:00 2001
From: Ronald Petty <ronald.petty@rx-m.com>
Date: Tue, 1 Nov 2022 10:52:39 -0700
Subject: [PATCH] Update pom.xml

Hi. Thanks for the examples. I am not 100% sure, but I suppose the log4j bugs are what caused these changes.

This tutorial:

https://docs.confluent.io/platform/current/schema-registry/schema_registry_onprem_tutorial.html#create-the-transactions-topic

does not seem to work with the existing pom.xml as the log4j packages moved / versioned. I am actually not sure why the confluent-log4j worked only with a version being set (instead of just taking the latest, maybe a Maven pro can confirm).

Thanks again.
---
 clients/avro/pom.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/clients/avro/pom.xml b/clients/avro/pom.xml
index 671c6e4f5..d83f16464 100644
--- a/clients/avro/pom.xml
+++ b/clients/avro/pom.xml
@@ -70,12 +70,13 @@ http://maven.apache.org/xsd/maven-4.0.0.xsd">
     </dependency>
     <dependency>
        <groupId>org.slf4j</groupId>
-       <artifactId>slf4j-log4j12</artifactId>
+       <artifactId>slf4j-reload4j</artifactId>
    </dependency>
    <!-- Use a repackaged version of log4j with security patches. Default log4j v1.2 is a transitive dependency of slf4j-log4j12, but it is excluded in common/pom.xml -->
     <dependency>
         <groupId>io.confluent</groupId>
         <artifactId>confluent-log4j</artifactId>
+        <version>1.2.17-cp10</version>
     </dependency>
   </dependencies>