Currently, all Spring Security's @Enable annotations are 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.
Currently, all Spring Security's
@Enableannotations are meta-annotated with@Configuration. While convenient, this is not consistent with the rest of the Spring projects and most notably Spring Framework's@Enableannotations.Additionally, the introduction of support for
@Configuration(proxyBeanMethods=false)in Spring Framework provides a compelling reason to remove@Configurationmeta-annotation from Spring Security's@Enableannotations and allow users to opt into their preferred configuration mode.