Does jakarta dependency update fit into Upgrade to Java 17?

[rogeriofrsouza]

Hey 👋🏻

After running the Migrate to Java 17 recipe in a personal project I realized it changed the javax packages to jakarta. I believe it's because of the Update jakarta.annotation-api dependency if it exists recipe.

But I wonder if this jakarta recipe should rather be placed inside Migrate to Spring Boot 3.0 or any of it sub-recipes, like Jakarta 9 or 10?
AFAIK, It seems that Spring Boot 2.x doesn't support jakarta, only javax.

So, is it a recommended approach to first migrate a Spring Boot 2.x to Java 17, test it, deploy and then, migrate to Spring Boot 3.x?

[timtebeek]

hi! Just three days ago we made some changes here: openrewrite/rewrite-migrate-java@a6a509e

• Improve "Add explicit Common Annotations dependencies" in "Migrate to Java 11" rewrite-migrate-java#816

Did you check this with the latest rewrite-migrate-java:3.15.0 ?
https://github.com/openrewrite/rewrite-migrate-java/releases/tag/v3.15.0

[rogeriofrsouza]

Hi, I just checked the Migrate to Java 17 in the latest 3.15.0

The project uses Java 11, Spring Boot 2.7, Maven build and a javax.validation.api dependency.
It's replacing all javax dependencies imports to jakarta, even though there is no jakarta dependency in the pom.xml

Idk if this was the expected behavior, but I had to manually undo these imports changes to test the Java 17 migration first.
My goal was to migrate to Spring Boot 3, so I had to change to Jakarta in the next recipe anyways.