b4c91e7dac
Prior to this commit, Spring offered two top-level implementations of the BeanNameGenerator strategy: DefaultBeanNameGenerator and AnnotationBeanNameGenerator. The latter is used as the default bean name generator for beans picked up via component scanning. In a typical application, this strategy works well; however, if multiple component scanned beans have the same simple class name (i.e., identical names ignoring the package), a BeanDefinitionStoreException is thrown. To address such naming conflicts, users of Spring have had to implement a custom BeanNameGenerator based on the fully qualified class name of such components. Similar conflicts can arise with components registered via configuration class imports (i.e., via @Import), and ConfigurationClassPostProcessor addresses this via an anonymous inner class that extends AnnotationBeanNameGenerator but falls back to using the fully qualified class name if an explicit bean name is not provided via an annotation. This commit extracts the implementation of ConfigurationClassPostProcessor's internal BeanNameGenerator into a new top-level FullyQualifiedAnnotationBeanNameGenerator class that can be used to disambiguate between same-named components residing in different packages that are picked up via component scanning. This bean name generator can be configured via @ComponentScan's nameGenerator attribute. Closes gh-24114
Spring Framework 
This is the home of the Spring Framework: the foundation for all Spring projects. Collectively the Spring Framework and the family of Spring projects are often referred to simply as "Spring".
Spring provides everything required beyond the Java programming language for creating enterprise applications for a wide range of scenarios and architectures. Please read the Overview section as reference for a more complete introduction.
Code of Conduct
This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.
Access to Binaries
For access to artifacts or a distribution zip, see the Spring Framework Artifacts wiki page.
Documentation
The Spring Framework maintains reference documentation (published and source), Github wiki pages, and an API reference. There are also guides and tutorials across Spring projects.
Build from Source
See the Build from Source Wiki page and the CONTRIBUTING.md file.
Stay in Touch
Follow @SpringCentral, @SpringFramework, and its team members on Twitter. In-depth articles can be found at The Spring Blog, and releases are announced via our news feed.
License
The Spring Framework is released under version 2.0 of the Apache License.