Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-7545

Explicitly import jakarta dependencies that are excluded via glassfish filter

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 2.6.0.Beta1
    • 2.6.0.Alpha2
    • debezium-server
    • None
    • False
    • None
    • False

      Currently, our dist module has an assembly config that states the following excludes:

      <exclude>org.apache.kafka:kafka-tools:*</exclude>
<exclude>javax.ws.rs:javax.ws.rs-api:*</exclude>
<exclude>org.apache.kafka:connect-file:*</exclude>
<exclude>org.glassfish.jersey.*:*:*</exclude>
<exclude>org.apache.maven:*:*</exclude>
<exclude>log4j:log4j:*</exclude>
<exclude>ch.qos.reload4j:reload4j</exclude>
<exclude>io.debezium:debezium-scripting</exclude>
<exclude>io.debezium:debezium-scripting-languages</exclude>
<exclude>io.debezium:debezium-connector-cassandra-3</exclude>
<exclude>io.debezium:debezium-connector-cassandra-4</exclude>
<exclude>io.debezium:debezium-connector-dse</exclude>

      One of the following, specifically this one

      <exclude>org.glassfish.jersey.*:*:*</exclude>

      causes some of the Jakarta libraries to be excluded and the debezium server won't start because it cannot find the class on classpath. So far, we have identified one specific case when this happens, and that is importing rocketmq storage

       

      A possible fix would be to find all the transitive Jakarta dependencies in glassfish jersey and add them to the second dependency set that specifically includes all found jakarta dependencies.

              obabec Ondřej Babec
              obabec Ondřej Babec
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: