Lab: Deprecated Properties & Runtime Errors ‐ 1: Overview - shinyay/spring-boot-2-7-to-3-1-upgrade GitHub Wiki

1: Overview Up to this point we've discussed the evolution of Spring projects over time. We've addressed dependency issues, code issues and deprecations, etc.

Just as Spring's code evolves, so has Spring's capability to manage configurations from external sources.

Property names will change over time. To assist with this migration, the Spring Maintainers have provided a library, spring-boot-properties-migrator, that will inspect your property configuration and provide you with errors and warnings based on the nature of change to the property itself.

The spring-boot-properties-migrator is a DEVELOPMENT ONLY library! The intention is to run the application locally, capture the output, address the needed property changes, then remove the dependency. Alternatively, you can comment out the dependency for future use.

This sounds an awful lot like the SCAR method, doesn't it?

Let's use the spring-boot-properties-migrator to inspect our own properties used in the Family Cash Card application, then migrate them as advised by the tool.

Review our Upgrade Notes Before we begin, remember that we're keeping detailed notes of the baseline state of our application as we upgrade it. Take a look at upgrade-notes.md to review where we are now.