Prior to this commit, the active bean definition profiles to use when
loading an ApplicationContext for tests could only be configured
declaratively (i.e., via hard-coded values supplied to the 'value' or
'profiles' attribute of @ActiveProfiles).
This commit makes it possible to programmatically configure active bean
definition profiles in tests via a new ActiveProfileResolver interface.
Custom resolvers can be registered via a new 'resolver' attribute
introduced in @ActiveProfiles.
Overview of changes:
Introduced a new ActiveProfilesResolver API.
Added a 'resolver' attribute to @ActiveProfiles.
Updated ContextLoaderUtils.resolveActiveProfiles() to support
Documented these new features in the reference manual.
Added new content to the reference manual regarding the
'inheritProfiles' attribute of @ActiveProfiles
Removed the use of <lineannotation> Docbook markup in the testing
chapter of the reference manual for Java code examples in order to
allow comments to have proper syntax highlighting in the generated
HTML and PDF.
You'll notice that I unfortunately wasn't able to merge your pull request directly due to significant changes in the 4.0 (i.e., master) branch; however, I was still able to use a lot of your code (albeit with some rather tedious copying-n-pasting ;)).
Also, your thorough unit and integration tests were especially helpful.