Prevent sagan-common from having Spring 3.2.x on its classpath

Spring Social GitHub has a transitive dependency on spring-webmvc
3.2.x. In the absence of any other spring-webmvc dependency, this
causes a mixture of Spring 3.2.x and Spring 4.0.x to be on
sagan-common's classpath.

This commit adds an explicit dependency on spring-webmvc. No version
number is specified to allow the version to be determined by the
Spring Boot plugin.

An alternative approach would be to use a resolution strategy:

configurations.all {
    resolutionStrategy {
        eachDependency {
            if (it.details.requested.group == 'org.springframework') {
                details.useVersion '4.0.5.RELEASE'
            }
        }
    }
}

Unfortunately, this approach requires you to specify the version of
Spring that you want to use, thereby preventing you from automatically
using the version that's provided by the Spring Boot plugin. There's
an issue open (spring-projects/spring-boot#932) to make the versions
available as properties, but, until that functionality is available,
I think the change made in this commit is the best solution.
Merge pull request #409 from wilkinsona/consistent-spring-version

Prevent sagan-common from having Spring 3.2.x on its classpath
Use a consistent version of HTTP client

Declare an explicit dependency on httpclient to stop io.searchbox:jest
from pulling in an old version. No version is declared so that the
Spring Boot plugin will determine the version. This change means that
sagan-common and sagan-site are built and tested against the same
version of httpclient.
Don't display search query in title tag

We shouldn't use unescaped text with user input.
See ultraq/thymeleaf-layout-dialect#46
Fix link to GH pull request instructions
Fix typo when reporting git branch for /info use

Thanks to Henning Hoefer's eagle-eyed observations at
https://vimeo.com/90956088#comment_11707853
Merge pull request #413 from cbeams/patch-1

Fix link to GH pull request instructions
Merge pull request #414 from cbeams/patch-2

Fix typo when reporting git branch for /info use
Upgrade to Boot 1.1.0.RELEASE

This commit updates Sagan to use Spring Boot 1.1.0.RELEASE.

Sagan's direct use of Flyway has been removed in favour of using the
Flyway auto-configuration that was added in Boot 1.1.0. To limit the
required configuration, the migration scripts have been moved to their
default location.

namingstrategy has been renamed to naming_strategy. While
namingstrategy will work with Boot 1.1.0 it has been deprecated in
favor of naming_strategy. For consistent use of camel case ddl-auto
has been renamed ddl_auto.

Boot 1.1.0 now provides auto-configuration for Spring Social. With
spring-social-web on the classpath it will auto-configure a
ConnectController. While Sagan has spring-social-web on its classpath
it does not use a ConnectController, therefore the auto-configuration
has been explicitly excluded.
Merge pull request #411 from wilkinsona/consistent-httpclient

Use a consistent version of HTTP client
Merge pull request #420 from wilkinsona/boot-1.1

Upgrade to Boot 1.1.0.RELEASE
Upgrade to Spring Boot 1.1.1
Delete PermGen options - useless for JDK8
Log Elastic Search failures

It may be sensible to fail softly when actions against Elastic Search fails for some reason, but not as soft as the current solution. Jest reports errors through `result.isSucceeded()` and `result.getErrorMessage()` (mapping errors and other).

This commit add WARN logging when `result.isSucceeded()` is `false` to make it easier to detect error situations.
Merge pull request #424 from bjornerik/log-elasticsearch-failures

Log Elastic Search failures
Update IO platform diagram with Spring XD status
Add Spring IO Platform to the project list
added Spring IO Platform to the list of active projects
Merge pull request #399 from bclozel/sagan-399

spring.io update for Spring IO Platform marketing launch June 17
Add 'stackoverflowtags' column to project table