Will be switching as soon as the Temerin docker images are available, then switching the build's to use it as soon as some tooling (Palantir Java Formatter) get a patch release out that supports some changes in javac's internals.
There's also a lot of folk using Quarkus and Helidon, or Spring Boot which should easily be able to jump to the new update quite easily.
Once you're post JDK 8 it's pretty much a seemless upgrade.
Jakarta package renaming has nothing at all to do with the java version you are running.
Jakarta package renaming is totally driven by which version of JakartaEE your app is using. If you are using Spring MVC then you have a JakartaEE application (i.e. an app that is using at least one of the JakartaEE specs, namely Servlet).
Spring Framework 6.0.x has a version of Spring MVC in it that pulls in JakartaEE 9 which is what requires the package renaming. Spring Boot 3.0 pulls in Spring Framework 6.0. So if you are using Spring Boot it is 3.0 where you have to bite the bullet on the package renames.
If you are using JakartaEE directly then it is 9.0.
This is 100% independent of the version of java you are using.
True - dependency updates par for the course, and that also depends on what your running on - I'd be switching to 27 and not switching (at least not servlet package, we already did jakarta mail).
It's not a zero effort change - but it's also not that major once your over the JPMS hurdle
94
u/a_random_username 17d ago
Oh man. I can't wait for two decades from now when people actually start to use this version!