Move away from spring.factories for auto-configuration imports #29745
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #29698
The most important changes are:
@AutoConfiguration
and the registration of those moved fromspring.factories
to the new file. Together with the changes in the selector this is now a backwards-compatible change. The spring.factories loading can be deprecated now and removed in 3.0.0@ImportAutoConfiguration
working, the selector has been updated and the documentation has been updatedspring.factories
to the new mechanism (here's the example for Cassandra)Task list
spring.factories
for auto-configuration.spring.factories
and the new entries.@AutoConfiguration
annotation which is meta-annotated with@Configuration
. The new annotation will defaultproxyBeanMethods
tofalse
.buildSrc
to read the new fileThe following nice-to-have tasks have been identified:
sed
)