On Wed, 6 Nov 2024 at 12:06, Christian Ortlepp wrote: > We don't really care at all about what the broker / server side > libraries do, since we don't have to integrate those with our application.
Thanks, that clarifies the requirement. > > The current target schedule is Pulsar 4.1 which is due in mid January. > > From this I'm guessing that Pulsar does not follow semantic versioning? Semantic versioning is followed. In this case, I don't think that we would be introducing actual breaking changes for Pulsar clients when we get rid of the unwanted dependencies. What is exactly the dependency that is causing problems? Are you also using the Pulsar Admin client? In that case, the open issue is https://github.com/apache/pulsar/issues/21297 . It looks like there are problems with the shading configuration of pulsar-client-all and pulsar-client-admin-shaded. There are transitive dependencies which should be shaded. This could be seen in the published pom.xml files (https://repo1.maven.org/maven2/org/apache/pulsar/pulsar-client-all/4.0.0/pulsar-client-all-4.0.0.pom and https://repo1.maven.org/maven2/org/apache/pulsar/pulsar-client-admin/4.0.0/pulsar-client-admin-4.0.0.pom). -Lari
