Migrate your own project
Support timelines
OSS support for Spring Boot 2.7 ended on November 18th, 2023, while support for Spring Boot 3.0 ended on November 24th, 2023. So if you haven't already, now's the time to migrate your project to Spring Boot 3.2!
Leap to Spring Boot 3.2
This guide will help you migrate your own project to Spring Boot 3.2. You've already seen how to run OpenRewrite recipes. If you need a recap and want to see detailed instructions, jump back to the Moderne CLI exercise.
To get started, you will want to run the migrate to Spring Boot 3.2 recipe, which runs you through all the steps of migrating to Spring Boot 3.2, 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.
Let's use the migrate to Spring Boot 3.2 recipe as an example:
This recipe is composed of 7 recipes. You can uncheck the recipes you don't want to run to reduce the scope of the changes. Or, if you want to learn more and reduce the scope further, you can click on one of the recipes.
For instance, if you click on the migrate to Spring Boot 3.0 recipe, you can see that it's composed of many recipes such as migrate to Spring Boot 2.7 and migrate to Java 17.
You can continue down this chain as much as you want. You can also pick out specific migrations that target specific components you're not up-to-date with, such as:
Migrate to Java 17, which of course includes Migrate to Java 11
Best practices after you migrate
After you've migrated to Spring Boot 3.2, 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:
Last updated
