Next development version
Fixup version numbers following release
Fix management endpoint without Spring Security

The method 'injectIntoSecurityFilter' added In 3c1e48c assumes that
Spring security is in the classpath so any management endpoints that are
deployed on a different port requires Spring Security all the sudden.

This commit separates the creating of the EndpointHandlerMapping in two
mutually exclusive @Configuration: one that is triggered if Spring
Security is not in the classpath and one that is triggered if Spring
Security is in the classpath. The latter apply the security filter in the
endpoint mapping if it exists.

Fixes gh-2124
Improve property target name

Previously, non camel case properties were wrongly resolved, i.e.
getFOO() leading to a 'f-o-o'. While unusual, underscores can also be
added to a property name. In that case, the hyphen should not be added
as the binder consider this to be a single "word". Typically setFoo_Bar
on the "something" prefix is mapped using "something.foo_bar".

All these cases are now handled properly, generating the target name that
the binder expects.

Fixes gh-2118
Properly guard ManagementSecurityAutoConfiguration

ManagementSecurityAutoConfiguration fully relies on the presence of a
web environment, yet the configuration class itself was not guarded by
`@ConditionalOnWebApplication` (while nested config where).

This turned out to be a problem for command-line applications using
spring security (i.e. CRaSH integration).

Fixes gh-2112
Properly document health indicator config

Health indicator configuration keys have moved from the health.* to the
management.health.* namespace. This commit makes sure that these are
documented properly in 1.1.x as well.

See gh-2118
Merge branch '1.1.x'
Add explicit reference to health.*

Health indicator configuration keys have moved from the health.* to the
management.health.* namespace. This commit adds an explicit reference
to the previous location.

See gh-2128
Polish indent
Merge branch '1.1.x'
Polish
Restore Spring Boot 1.1 logging behavior

Refactor LoggingApplicationListener and LoggingSystem to restore
Spring Boot 1.1 logging behavior. The LOG_FILE and LOG_PATH system
properties are now set before configuring the logger.

The `logging.path` property is now once again optional and will not be
used when `logging.file` is specified. The documentation has also been
updated to reflect the changes.

Fixes gh-2121
Fixes gh-2117
Substitute ${PID} variables with file logging

Update DefaultLogbackConfiguration to include OptionHelper.substVars
when setting the encoder pattern so that ${PID} is correctly expanded.

Fixes gh-2119
Unify console and file logback patterns

Update the file log pattern to write the thread name after the `---`
separator. The allows both file and console logs to be parsed in the
same way.

Fixes gh-2136
Adding meta-data for spring.output.ansi.enabled

Closes gh-2145
Polish
Protect against null CodeSource location

Update LogbackLoggingSystem to protect against a potential null
CodeSource result.

Fixes gh-2149
Merge branch '1.1.x'

Conflicts:
	spring-boot/src/main/java/org/springframework/boot/StartupInfoLogger.java
	spring-boot/src/main/java/org/springframework/boot/logging/logback/LogbackLoggingSystem.java
Fix banner NPE when when using the default package

Update ResourceBanner to protect against a null application package.

Fixes gh-2143
Upgrade to SLF4J 1.7.8

Closes gh-2151