Latest dependency updates (Jackson 2.4, Jetty 9.2.1, H2 1.4.178, Apache HttpClient 4.3.4)
ObjectToOptionalConverter needs to be marked as @UsesJava8
update documentation with latest forum infos

Forums will be shortly deactivated and questions should take place
in StackOverflow.
Defensively check javaUtilOptionalEmpty

Issue: SPR-11888
Defensively check javaUtilOptionalEmpty

Issue: SPR-11888
MBeanExportConfiguration's SpecificPlatform properly calls afterPropertiesSet

Also makes the nested SpecificPlatform enum public for Spring Boot to reuse it.

Issue: SPR-11877
WebSphereUowTransactionManager exposes SmartTransactionObject

Issue: SPR-11876
PathMatchingResourcePatternResolver's findPathMatchingResources needs to check for VFS before checking isJarResource

Issue: SPR-11887
ResourceUtils isFileURL detects "vfsfile" as a file system protocol (again)

Issue: SPR-11887
Rename SQL script annotations in the TCF

Prior to this commit, SQL script annotations and related classes in the
TestContext framework (TCF) were named DatabaseInitializer*. However,
these annotations are not used only for initialization and are
therefore misleading when used for cleaning up the database.

This commit refines the names of annotations and related classes for
configuring SQL scripts to be executed for integration tests in the TCF
as follows:

- @DatabaseInitializer -> @Sql
- @DatabaseInitializers -> @SqlGroup
- DatabaseInitializerTestExecutionListener -> SqlScriptsTestExecutionListener

A special thanks goes out to the following attendees of the Zurich
Hackergarten meeting last night for their collective brainstorming:
@aalmiray, @atsticks, @ollin, @simkuenzi, @tangresh, @vyazelenko.

Issue: SPR-7655
Introduce repeatable @Sql tests

This commit introduces explicit integration tests that verify Java 8's
@Repeatable support for the @Sql annotation.

Issue: SPR-7655
Delete remaining SimpleJdbcTemplate usage

This commit deletes all remaining usage of the deprecated
SimpleJdbcTemplate class within the framework itself.

Issue: SPR-11895
AnnotationUtils defensively catches unexpected exceptions from retrieval attempts (proceeding like the annotation wasn't there)

This is analogous to what the JVM does for cases where the annotation type itself isn't present on the classpath. We're effectively extending that policy to values referenced within an annotation declaration.

Issue: SPR-11874
AnnotationUtils defensively catches and logs unexpected exceptions from retrieval attempts (proceeding like the annotation wasn't there)

Issue: SPR-11874
Consistent declaration of private static final logger variables

Issue: SPR-11905
Refactor VersionResourceResolver in strategies

Prior to this commit, one of the available strategies for resolving
resources was the PrefixResourceResolver. Reconsidering the core goal of
this resolver and the FingerprintResourceResolver, we found that the
true core feature is versioning static resources application-wide.

This commit refactors both Resolvers by:
* having only on VersionResourceResolver
* that resolver takes a mapping of paths -> VersionStrategy
* provided VersionStrategy implementations are ContentBasedVS
  (previously FingerprintRR), FixedVS (previously PrefixRR)

One can add a VersionResourceResolver like this:

  Map<String, VersionStrategy> versionStrategies = new HashMap<>();
  versionStrategies.put("/**/*.js", new PrefixVersionStrategy("prefix"));
  versionStrategies.put("/**", new ContentBasedVersionStrategy());

  VersionResourceResolver versionResolver = new VersionResourceResolver();
  versionResolver.setVersionStrategyMap(versionStrategies);

  List<ResourceResolver> resolvers = new ArrayList<ResourceResolver>();
  resolvers.add(versionResolver);
  resolvers.add(new PathResourceResolver());

Issue: SPR-11871
Preparations for eventual removal of ParameterizedRowMapper along with SimpleJdbcTemplate

Issue: SPR-11895
TypeDescriptor's nested type traversal leniently returns null in case of unresolvable nested type

Issue: SPR-11898
Avoid pattern matching in isCglibRenamedMethod as far as possible (for performance reasons)

Issue: SPR-11894
FrameworkPortlet exposes local PortletRequestAttributes in case of pre-bound ServletRequestAttributes as well

Issue: SPR-11295