Hi Ismael,
Thanks for the feedback, I can definitely raise a KIP, that is no problem.
I will write one up and then we can have further discussion on the details.
I should have time to get one created later today or by tomorrow.
Chris
On Wed, Mar 27, 2024 at 11:54 AM Ismael Juma wrote:
> Hi
Hi Christopher,
Thanks for raising this. Moving to the new namespace makes sense - would
you be willing to submit a KIP? The point you raised regarding Jetty 11 EOL
and Jetty 12 requiring Java 17 is a good one and is worth discussing the
trade-offs in more detail. I originally did not propose
Greg,
I definitely understand that part, it's always tricky for users that have
older software and haven't or can't upgrade yet.
The most important thing to me is getting to the new Jakarta APIs and Java
EE updates as that causes incompatibilities with code and requires code
changes. So if that
Hey Christopher,
Thank you for explaining that jetty version dependency, I was not aware of that.
> So are we really locked into JDK 11 for Connect for version 4.0?
Until we adopt a KIP to change the minimum version, we must support 11
in 4.0. By default we will continue to support Java
Hi Greg,
You are right that KIP-1013 and the JDK 17 upgrade is not directly relevant
because JDK 11 can still be used with Jakarta APIs. However, it's still
somewhat relevant and important because if we are stuck at JDK 11 then we
can't upgrade to certain versions. For Connect, there is a Jetty
Hi Christopher!
Thanks so much for raising this. I agree that we should move to the
new namespace in 4.0, and not doing so would be a mistake.
This breaking change has a lot of benefits, and the only cost I am
aware of is that ConnectRestExtensions will need to be migrated,
rebuilt, and
Is this already being planned for version 4.0? If not, I strongly thing it
should be.
Kafka is currently using the old long deprecated javax apis which is going
to continue to cause issues [1] for people as more and more things are
updated to use Jakarta.
With the bump to require JDK 17 for
