Detecting property changes
As we learned in this book, one of the main tasks when developing a Spring Boot application is configuring its components. It’s important to note that every time a new component version is released, there may be changes to the properties. This is especially true when upgrading to a major version, such as from version 2.x to 3.0. Typically, the changes are gradual. For example, a property might be marked as deprecated in one version, meaning it will be removed in a future version. Therefore, it’s recommended not to skip any versions when upgrading. For instance, if you plan to upgrade from version 2.6 to version 3.2, it’s best to upgrade first to version 2.7, then to 3.0, then 3.1, and finally 3.2.
To address the property changes between versions, Spring Boot provides a tool named Spring Boot Properties Migrator. It’s a dependency that analyzes the application environment during the application start-up and prints a diagnostic...
