Release version 3.2.2.RELEASE
Increment version to 3.2.3.BUILD-SNAPSHOT
Update copyright year in reference documentation
Fixed Jaxb2Marshaller's partial unmarshalling feature to consistently apply to all sources

Issue: SPR-10282
Fixed ReflectiveMethodResolver to avoid potential UnsupportedOperationException on sort

Issue: SPR-10392
Preparations for 3.2.3
Defensively uses JDBC 3.0 getParameterType call for Oracle driver compatibility

Issue: SPR-10385
Introduced public ArgumentPreparedStatementSetter and ArgumentTypePreparedStatementSetter classes

Issue: SPR-10375
Removed unnecessary default value of LifecycleGroup.lifecycleBeans

Issue: SPR-10388
JdbcTemplate etc
Added "destroyBean(Object)" method to AutowireCapableBeanFactory

Driven by the need for implementing Bean Validation 1.1's "releaseInstance" method in SpringConstraintValidatorFactory, as a direct counterpart to the use of AutowireCapableBeanFactory's "createBean(Class)" in "getInstance".

Issue: SPR-8199
Initial support for Bean Validation 1.1 and Hibernate Validator 5.0

MethodValidationInterceptor autodetects Bean Validation 1.1's ExecutableValidator API now and uses it in favor of Hibernate Validator 4.2's native variant.
SpringConstraintValidatorFactory implements Bean Validation 1.1 "releaseInstance" method against new "destroyBean(Object)" method in AutowireCapableBeanFactory.
LocalValidatorFactoryBean adapts Spring-provided ParameterNameDiscoverer onto Bean Validation 1.1's ParameterNameProvider mechanism.
LocalValidatorFactoryBean reflectively adapts between the different ResourceBundleLocator SPI location in Hibernate Validator 4.2 versus 5.0.
LocalValidatorFactoryBean implements Bean Validation 1.1 "close" method.

Note: We still compile against Bean Validation 1.0 in order to not have to implement "forExecutables()" and "getParameterNameDiscoverer()" in LocalValidatorFactoryBean, SpringValidatorAdapter and CustomValidatorBean. Implementing those methods would imply references to Bean Validation 1.1 interfaces that break runtime compatibility with Bean Validation 1.0. Unfortunately, this means that all Bean Validation 1.1 API access has to be done via reflection.

Issue: SPR-8199
Consistently refer to most recent version of javax.el, in order to be compatible with Hibernate Validator 5.0 when doing integration tests

Issue: SPR-8199
Use JDK 1.6's Collections.newSetFromMap instead of manually accessing Maps with dummy Boolean values
Added "destroyBean(Object)" method to AutowireCapableBeanFactory

Driven by the need for implementing Bean Validation 1.1's "releaseInstance" method in SpringConstraintValidatorFactory, as a direct counterpart to the use of AutowireCapableBeanFactory's "createBean(Class)" in "getInstance".

Issue: SPR-8199
Upgraded JdkVersion and CollectionFactory to JDK 1.6+, also removing deprecated methods from CollectionFactory
Fully upgraded orm.hibernate3 package to require Hibernate 3.6+ now
Removed deprecated saveOrUpdateAll method from HibernateOperations
Removed deprecated JdoTemplate and JdoInterceptor classes; formally requiring JDO 3.0+ now
Removed deprecated JpaTemplate and JpaInterceptor classes; dropped unused EntityManager(Factory)Plus mechanism