Now that we expect auto-configurations to be registered in an alternative mechanism, we should provide some sort of warning/exception for those who are in spring.factories still.
When looking into this, we should consider the case of a starter offering support for both the old and the new mechanism and only considering this as an error if the auto-configuration is only registered in spring.factories.
To avoid doing this search on startup, perhaps we should consider giving this extra information when the application has failed to start?
Comment From: philwebb
Given the limited amount of time left, and the fact that this mainly affects integrators I'm tempted to close this and rely on the release notes instead. Flagging for team opinions.
Comment From: snicoll
Another option would be to expand spring-boot-properties-migrator to look for that pattern and warn users about it.