Remove Configuration meta-annotation from Enable* annotations #11653
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.
Before, Spring Security's @enable* annotations were meta-annotated with @configuration.
While convenient, this is not consistent with the rest of the Spring projects and most notably
Spring Framework's @enable annotations. Additionally, the introduction of support for
@configuration(proxyBeanMethods=false) in Spring Framework provides a compelling reason to
remove @configuration meta-annotation from Spring Security's @enable annotations and allow
users to opt into their preferred configuration mode.
Closes gh-6613
Signed-off-by: Joshua Sattler [email protected]