FullyQualifiedConfigurationBeanNameGenerator as introduced in 7.0 (#33448) involves a different naming policy for @Bean-derived beans in case of no explicit bean name specified. This may have wide-ranging impact even for internal configuration classes and Boot auto-configuration, in particular if the default bean names are expected to be stable for injection by name. We need to document the impact of such a change and potentially introduce ways of narrowing the applicability to specific application packages only.
FullyQualifiedConfigurationBeanNameGeneratoras introduced in 7.0 (#33448) involves a different naming policy for@Bean-derived beans in case of no explicit bean name specified. This may have wide-ranging impact even for internal configuration classes and Boot auto-configuration, in particular if the default bean names are expected to be stable for injection by name. We need to document the impact of such a change and potentially introduce ways of narrowing the applicability to specific application packages only.