Add spring-boot-dependencies to prepare phase
Next development version
Fixup version numbers following release
Support for Jmx (and Integration) autoconfig in parent contexts

When there are parent contexts we already had a strategy for registering
the actuator endpoints, but not the regular JMX or Integration MBeans.
This chnage makes the autoconfigs for JMX aware of the parent context.

Also adds a sample with a parent context.

See gh-847
Roll back to 1.1.0.BUILD-SNAPSHOT
Use classname instead of value in @ConditionalOnMissingClass

See gh-1065
Deprecate @ConditionalOnMissingClass.value

Fixes gh-1069
Remove superfluous starter dependencies

Remove superfluous dependencies from spring-boot-starter-tomcat and
spring-boot-starter-jetty which caused gradle based builds to put
too many libraries in `/lib-provided` when building a war.

Fixes gh-1064
Next development version
Fixup version numbers following release
Resolve versionManagement configuration lazily and preserve exclusions

Previously, the versionManagement configuration was resolved as part of
the Boot Gradle plugin being applied. This meant that no dependencies
could be added to it and attempting to do so would result in a failure:
“You can't change a configuration which is not in unresolved state”.
This commit updates ApplyExcludeRules to wrap its processing in a
before resolve action. This defers the resolution of the
versionManagement configuration until one of the project’s other
configurations is being resolved. Fixes #1077

In addition to the above, the transitive exclusions that the Gradle
plugin provides were being lost if custom version management provided
a version for the same dependency. This commit updates
AbstractDependencies to preserve the exclusions from an existing
dependency declaration while using the version from the newer
dependency. This ensures that the exclusions remain while allowing
versions to be overridden. Fixes #1079
Test for message properties
Defensive null check in case Hibernate autoconfig is off

If the Hibernate autoconfig is not used to create an EntityManager
then I suppose it's possible that the JpaProperties might be null
when everything else is ready for the event to be published.

There's no test case because I think it's a corner case.

Fxies gh-1075
Add tests for switching message sources in tests

See gh-1075
Switch mergeDependencies to use a set.
Next development version
Fixup versions following release
Fix typo in reference docs appendix

Fixes gh-1082
Merge pull request #1082 from emalock3/patch-1

* patch-1:
  Fix typo in reference docs appendix
Add clarification of ddl-auto and schema.sql