QualifierAnnotationAutowireCandidateResolver matches regular bean name for FactoryBean dependency type as well
Upgraded to Apache HttpComponents HttpClient 4.3.1 and HttpAsyncClient 4.0 GA, as well as Jackson 2.2.2
GenericTypeResolver's resolveTypeArguments needs to return null for raw types (for backwards compatibility with 3.2)

Issue: SPR-11052
Tweak method signatures in HttpComponentsClientHttpRF

This change replaces CloseableHttpClient with HttpClient in the
methods signatures of HttpComponentsClientHttpRequestFactory.
This allows 3rd party libraries such as Spring OAth, which configure
an instance of HttpComponentsClientHttpRequestFactory on the
RestTemplate to remain compatible with both Spring Framework 3/4

Issue: SPR-11053
Release version 4.0.0.RC1
Increment version to 4.0.0.BUILD-SNAPSHOT
Avoid unnecessary char[] allocation in NamedParameterUtils

Issue: SPR-11042
LocaleContextHolder allows for independent setting of Locale and TimeZone

Issue: SPR-1528
Avoid potential NPE in toString()

Issue: SPR-1528
Added further author tags

Issue: SPR-1528
Polished exception messages

Issue: SPR-11042
Introduced setCacheRegionFactory method on LocalSessionFactoryBuilder/Bean

Issue: SPR-11056
Added convenience classes for typical JSR-236 setup in a Java EE 7 environment

Introduced DefaultManagedTaskExecutor, DefaultManagedTaskScheduler and DefaultManagedAwareThreadFactory classes, revised related javadoc, and deprecated unsupported JBossWorkManagerTaskExecutor in favor of JSR-236 setup on WildFly 8.

Issue: SPR-8195
Use non-lenient constructor resolution mode for @Bean methods

Since @Bean methods are never used with externally specified constructor argument values but rather just with autowiring, the non-lenient constructor resolution mode is appropriate in case of an overloaded @Bean method, not performing any type difference weight checks. This change includes a refinement of Spring's existing non-lenient constructor resolution (which needs to be explicitly turned on and is therefore not well tested), narrowing the conditions for the ambiguity check (only in case of the same number of arguments and not for overridden methods).

Issue: SPR-10988
Added get(key, type) method to Cache interface

This new get variant not only allows for generically specifying the required value type; it also skips the ValueWrapper that the standard get method returns. Note that it is not possible to differentiate between non-existing cache entries and cached null values that way; for that purpose, the standard get variant needs to be used.

Issue: SPR-11061