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 re-released for 4.0+
Can you explain how KIP-1013 and the Java version are relevant? Connect is dependent on this namespace, but will still need to support Java 11 in 4.0. Thanks! Greg On Tue, Mar 26, 2024 at 5:04 AM Christopher Shannon <christopher.l.shan...@gmail.com> wrote: > > 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
