> 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
> The benefit of moving towards PulsarTestContext as the way to wire up things
> is that PulsarTestContext could also be used in Junit 5 when we start
> migrating away from TestNG.
> Perhaps we could enable Junit 5 for new tests and start moving to this
> direction? In BookKeeper, Junit 5 is ena
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
Hi all,
I wrote a PIP (https://github.com/apache/pulsar/pull/23567) to enable
batch index ACK by default.
>From my experiences, the default ACK semantics are really confusing
and it's hard to explain the implementation details to users. Even if
it's explained, this design is still not convincing.
Hi, Lari.
I’d like to take it and handle it. I’m a new guy for Pulsar, but I wanna be a
contributor in the future. And probably I will trouble you if met some
questions.
And you could provide cook-books or links to show how to do release job, will
be so appreciated.
Regards
Vision
From: Lar
Hi,
In the Apache Pulsar project, we need more Pulsar committers and PMC members to
contribute to project administrative tasks. While we have 43 PMC members and 41
committers, very few are contributing to these administrative responsibilities.
For this project to succeed and grow, we need PMC m
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
