Migrate to Spring Boot 3.0
ProprietaryMigrate applications to the latest Spring Boot 3.0 release. This recipe will modify an application's build files, make changes to deprecated/preferred APIs, and migrate configuration settings that have changes between versions. This recipe will also chain additional framework migrations that are required as part of the migration to Spring Boot 3.0, including the Tomcat 10.1 upgrade which removes LegacyCookieProcessor, the Spring WS 4.0 migration off Apache Axiom, and the migrations off Spring Cloud AWS 2.x and spring-data-dynamodb, which have no Spring Boot 3 release. Modules that used Spring Cloud AWS 2.x also have their AWS SDK for Java v1 code migrated to v2, which io.awspring 3 requires. In spring-data-dynamodb modules only the code that uses DynamoDB is, as the generated repositories need a v2 client. The Amazon SQS Java Messaging Library moves to its jakarta.jms release, which is built on AWS SDK v2, along with the sources that use it. All other code keeps AWS SDK v1.
io. moderne. java. spring. boot3. UpgradeSpringBoot_3_0mod run . --recipe= io. moderne. java. spring. boot3. UpgradeSpringBoot_3_0Install it once from Recipe actions, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.
Recipe list
It runs these recipes, in this order.
- Migrate to Spring Framework 5.3
- Migrate to Spring Boot 3.0
- Migrate to Spring Batch 5.0
- Migrate to JSF 2.3
- Migrate to Spring Framework 6.0
- Use
Rfc6265CookieProcessorinstead ofLegacyCookieProcessor - Migrate to Spring WS 4.0
- Migrate to Spring REST Docs 3.0
- Migrate AWS libraries that have no Spring Boot 3 release