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 version 4.0 [2] this seems like the perfect time to upgrade to a new version of JavaEE and Jakarta apis and new versions of dependencies like Jackson, Jersey, Jetty (12.x), etc that all support the new namespace. It needs to be upgraded at some point anyways so a major version makes sense to me. Another scenario where I've run into this problem is testing. For example, If I try to run tests against my custom code with an embedded Kafka broker and components in JUnit, then things break with newer dependencies like Spring that require Jakarta as it interferes on the classpath. [1] https://issues.apache.org/jira/browse/KAFKA-16326 [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789510
