> Semantic versioning is followed.

Even if no Jakarta Interfaces/Annotations are part of Pulsars public API, switching to jakarta can (and probably will) mess with the dependency resolution of everybody who uses the client. So I do think this is a breaking change, even if no javax/jakarta interfaces are used explicitly anywhere in Pulsars API.

> It looks like there are problems with the shading configuration of

pulsar-client-all and pulsar-client-admin-shaded.

We are just using the pulsar-client. I also did not know that pulsar shades its dependencies, but from a quick look at the pom it looks to me that (of the javax libraries) it only shades javax.annotation, but not javax.ws.rs-api, javax.activation, javax.validation. But this is just what I'm reading from the POM, I have not tried it out yet. So I also do not have any acute problems yet, but I will IF pulsar actually needs any of the javax libraries like it advertises this in the POM (if it shades them all I should not have any problems).

I am honestly a bit confused at the moment, is what is published on maven central as "pulsar-client" actually "pulsar-client-shaded"?


Christian


On 06.11.24 14:06, Lari Hotari wrote:
External Message - Please be cautious when opening links or attachments


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 ishttps://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
andhttps://repo1.maven.org/maven2/org/apache/pulsar/pulsar-client-admin/4.0.0/pulsar-client-admin-4.0.0.pom).

-Lari

Reply via email to