https://github.com/apache/pulsar/pull/23647 addresses the pulsar-client
(shaded), pulsar-client-admin (shaded and pulsar-client-all (shaded) shading
issues where javax.annotation was exposed,
https://github.com/apache/pulsar/issues/21297 . The issues have been resolved
by migrating some annotat
On Thu, 7 Nov 2024 at 07:38, Christian Ortlepp wrote:
>
> > 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
> 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 inte
Just curious to know your requirements. Are you primarily interested
in Jakarta dependencies in the Pulsar Java client or do you have
requirements for the broker / server side libraries of Pulsar. What is
your primary motivation? Explaining that could help take your explicit
requirements into cons
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
On Wed, 6 Nov 2024 at 09:35, Christian Ortlepp wrote:
>
> Thank you for the information and sorry for the late reply, I had to
> discuss this with some of my colleagues first. Currently we are still
> working on migrating some other libraries to jakarta that have a higher
> priority for our project
Thank you for the information and sorry for the late reply, I had to
discuss this with some of my colleagues first. Currently we are still
working on migrating some other libraries to jakarta that have a higher
priority for our project, but it is possible that we will come back to
this at a lat
In the Pulsar code base, there are some dependencies to javax / Java
EE interface libraries due to Jetty 9.4.x dependencies.
It will be necessary to upgrade to Jetty 12
(https://github.com/apache/pulsar/issues/22939) in order to get rid of
javax / Java EE interfaces in the Pulsar codebase.
In Jetty
