6641dbc852
Prior to this commit (and since Spring Framework 5.0), Spring's integration with JUnit Jupiter supported detection of test configuration (e.g., @ContextConfiguration, etc.) on @Nested classes. However, if a @Nested class did not declare its own test configuration, Spring would not find the configuration from the enclosing class. This is in contrast to Spring's support for automatic inheritance of test configuration from superclasses. The only workaround was to copy-n-paste the entire annotation configuration from enclosing classes to nested tests classes, which is cumbersome and error prone. This commit introduces a new @NestedTestConfiguration annotation that allows one to choose the EnclosingConfiguration mode that Spring should use when searching for test configuration on a @Nested test class. Currently, the options are INHERIT or OVERRIDE, where the current default is OVERRIDE. Note, however, that the default mode will be changed to INHERIT in a subsequent commit. In addition, support will be added to configure the global default mode via the SpringProperties mechanism in order to allow development teams to revert to the behavior prior to Spring Framework 5.3. As of this commit, inheritance of the following annotations is honored when the EnclosingConfiguration mode is INHERIT. - @ContextConfiguration / @ContextHierarchy - @ActiveProfiles - @TestPropertySource / @TestPropertySources - @WebAppConfiguration - @TestConstructor - @BootstrapWith - @TestExecutionListeners - @DirtiesContext - @Transactional - @Rollback / @Commit This commit does NOT include support for inheriting the following annotations on enclosing classes. - @Sql / @SqlConfig / @SqlGroup In order to implement this feature, the search algorithms in MetaAnnotationUtils (and various other spring-test internals) have been enhanced to detect when annotations should be looked up on enclosing classes. Other parts of the ecosystem may find the new searchEnclosingClass() method in MetaAnnotationUtils useful to provide similar support. As a side effect of the changes in this commit, validation of user configuration in repeated @TestPropertySource declarations has been removed, but this may be reintroduced at a later date. Closes gh-19930
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.
Micro-Benchmarks
See the Micro-Benchmarks Wiki page.
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.