Migrate your own project

Support timelines

OSS support for Spring Boot 2.7 will end on November 18th, 2023, while support for Spring Boot 3.0 will end on November 24th, 2023. So if you haven't already, now's the time to migrate your project to Spring Boot 3.1!

Leap to Spring Boot 3.1

This guide will help you migrate your own project to Spring Boot 3.1. You've already seen various ways of running OpenRewrite recipes by now; pick the one that best suits your project for this migration. For a recap and detailed instructions see each of the indivual exercises:

You will want to run the Migrate to Spring Boot 3.1 recipe, which runs you through all the steps of migrating to Spring Boot 3.1, no matter what version you're coming from.

Migrate in steps

If you'd rather migrate in steps, you can also run recipes individually. This can be helpful if you'd like to review and build confidence in the changes, or need to troubleshoot a particular aspect.

As you can see in the Migrate to Spring Boot 3.1 recipe, that first takes you to Spring Boot 3.0, which first takes you to Spring Boot 2.7, which first takes you to Spring Boot 2.6, ... You can run any of these intermediate recipes, to pick up the changes up to that point.

You can also pick out specific migrations, for as much as you aren't up-to-date already, such as:

Migrate Spring Boot 2.x projects to JUnit 5 from JUnit 4
Migrate to Java 17, which of course includes Migrate to Java 11
Migrate to Spring Security 5.8
Spring Boot 2.x best practices

Best practices after you migrate

After you've migrated to Spring Boot 3.1, you might want to consider some of the following best practices:

You might even want to run some of these recipes periodically, to keep your projects up-to-date continuously.

Helpful resources

Here's a number of links that might be helpful in case you encounter edge cases not yet covered:

4.7 KiB Raw Blame History