Temporarily remove the spring-data release train BOM since it cannot
be resolved until it is published to maven central.

The previous solution of adding an additional repository has been
reverted as it will pollute POMS for users that inherit from the
spring-boot-starter-parent POM.

This reverts commit 1ef3d3bd.

For the convenience of users who want to selectively override the
access rules in an application without taking complete control of the
security configuration we now have some constants:

* SecurityProperties.ACCESS_OVERRIDE_ORDER for overriding just the
application endpoint access rules

* ManagementServerProperties.ACCESS_OVERRIDE_ORDER for overriding the
application endpoint and management endpoint access rules

Fixes gh-803

The transitive dependency org.neo4j:neo4j-cypher-dsl:2.0.1 isn't
available in Maven Central. This was leading to frequent build breaks
so we've decided to remove the Neo4J starter until all of its
dependencies can be resolved from Maven Central.

Fixes #797

This brings Boot's dependency management into line with the version
of GemFire used by Spring Data GemFire in the Dijkstra release train

Upgrade to latest version of AspectJ and provide dependency management
for all of its modules.

This (empirically) fixes gh-726 using a new utility
(LogbackInitializer) in the loader tools. If anyone has enough
Gradle fu to understand where to put it (after the classpath is established
but before compilation) we could do the same thing in the Gradle plugin
(and that would fix gh-724).

All dependencies have recently moved to the spring-boot-dependencies
POM but that POM does not contain the repositories that are required to
download milestone artifacts.

This commit moves the default profile that is active by default at the
right place in the hierarchy so that it is applied there as well.

In addition to the upgrade to Dijkstra (#743) Spring HATEOAS has been
upgraded to 0.11.0 (#801) and Mongo's Java driver has been upgraded to
2.12.1 (#689). In both cases this is the same version as is used by
Dijkstra RC1.

The new version of Mongo's Java driver changes the exception that's
thrown when Mongo isn't running and a connection attempt fails. The
Mongo sample has been updated accordingly.

RepositoryRestMvcAutoConfiguration has been updated to be configured
before JpaRepositoriesAutoConfiguration. This ensures that the
former's transitive import of SpringDataJacksonConfiguration takes
precedence over the latter's import of the same. This is necessary as
RepositoryRestMvcConfiguration requires a bean that's declared by
SpringDataJacksonConfiguration and, if JpaRepositoriesAutoConfiguration
is processed first, its conditions may cause the import
SpringDataJacksonConfiguration to be skipped causing instantiation
of RepositoryRestMvcConfiguration to fail.

Closes #689
Closes #743

Replace the `spring-boot.version` property with a hard-coded value,
rather than relying on the parent version. Allows locally installed
snapshots to be used as the parents of projects with a different version
number.

Upgrade to latest release of Spring AMQP and provide dependency
management for all of its modules

Closes #799

Closes #397 and #717

This commit provides several options to exclude one or more
dependencies:

* excludes allows to specify an arbitrary number of exclude sub
  element defining the groupId and artifactId of the dependency
  to exclude
* excludedGroupIds defines the comma separated list of groupIds
  to exclude
* excludeArtifactIds defines the comma separated list of artifactIds
  to exclude

While any artifact can be excluded, this is designed to exclude
provided-scoped dependencies that should not be bundled in the
executable jar/war.

The outcome of java -jar myapp.jar should be consistent with the run
goal: these exclusions are therefore applied to the classpath that
the run goal computes to launch the application.

This commit also adds some integration tests and updates the
plugin's documentation

Fixes gh-649, gh-650 and gh-674

Update documentation to use a real auto-configure class.

Fixes #791

fixes #587 and #588

fixes #791

Upgrade Boot to use Groovy 2.3.0 and provide dependency management
for all of Groovy's modules.

Closes #647

* module-version-mgt:
  Fixup reference guide following dependencies move
  Fixup POM harmonization
  Harmonized maven dependency management

Update reference guide to indicate that spring-boot-dependencies should
be imported when not using the parent POM.

Fix POM harmonization so that the release process now
prepares the dependencies POM rather than starter-parent

This commit harmonizes the dependency management of internal modules
so that versions can be omitted everywhere. Update the maven coordinates
to provide the full groupId for consistency

Freemarker integration tests now use a random port so boot
builds properly when port 8080 is taken.

Update the reference guide to add a call-out to the new generated
maven plugin site.

Finishes gh-772

* pull780:
  Add multi-datasource health indicator support
  Add CompositeHealthIndicator

Update EndpointAutoConfiguration to support multiple datasources.

Fixes gh-783

Add CompositeHealthIndicator that allows multiple HealthIndicators
to be combined into a single result.

Fixes gh-782

* docfix:
  Minor documentation fixes

Fixes gh-781

Previous to this commit, the remote shell security configuration
described that a default password will be generated with no extra
configuration. Actually, when Spring Security is configured for the
application, the remote shell reuses that configuration by default.

It turns out that the default log message is confusing as it was
referring to "application endpoints". Updated that log to a more
generic log message and updated doc accordingly.

Fixes gh-779

Fixes gh-778, Fixes gh-755

Fixes gh-776