With this change it is possible to include credentials in the instance
metadata which will then be used to access the client endpoints using
HTTP Basic authorization.

closes #359

With this commit you can now associate your applications with custom
metadata using `spring.boot.admin.client.metadata.*` sensitive values
are recognized by key and are masked in the http interface.

This can be useful in the future if there are instance specific settings
which should be used by the admin server, e.g. custom notification
recipients.

For now there is no extra imetadata view in the ui. The values are shown
in the environment view.

With this commits the server no longer depends on the client. The
classes for the clients are moved to de.codecentric.boot.admin.client
package.
Since the perspective on applications is totally different from client
and server the model has been split apart.

What means this for users:
1) The client is no longer a transitive dependency for your admin server
you may need to add it explicitly to your dependencies, respectively
jolokia-core in case you're using discovery and want to use the jmx-bean
interface

2)In case you have cutomised parts of the client you need to reflect the
package change.

fixes #332

With this commit the support for Turbine is completly revised. From now
on Turbine is supported via a separate module and is integrated as top
level view.

closes #306

closes #299

By using the netflix/hystrix-dashboard this module allows you to view the
metrics from hystrix/turbine in the spring boot admin server. This module needs
to be added explicitly.

closes #147

As now with spring boot 1.4 there is a special goal for generating the build-
information, we use it for displaying the version in spring boot admin. The old
info.version property still works but is deprecated. From now on
build.info.version is taken into account.

The 1.4.0 release was a total disaster. Webpack didn't build the css correctly
because of travis using an ancient nodejs version.

With this commit urls form the /info endpoint are deteceted and rendered as
links.
The downside is to make that work I had to drop the collapsible info section in
the overview list and replaced it with an resizable/scrollabe <pre> section.

fixes #205

This adds a new FilteringNotifier which can use filters to suppres certain
events from being notified of. Two filter implementation are provided, one
filtering by name and one by id. Additional when a FilteringNotifier bean is
present, the autoconfiguration creates a REST-controller to add and remove
filters at runtime.

The polling in the UI is replaced with server side events. Status changes are
now reported immediately from the admin server to the UI.

Remove the git-commit-id-plugin from the sample and don't fail in docs when the
sources are not located in an git-repository (e.g. downloaded from zip)

I did an accidental release of a 1.3.2, so we need another increment

Deriving from Spring Clouds ProxyRouteLocator has become too difficult. It would
have required to either set fixed ZuulProperties or providing a DiscoveryClient.
So we are shipping our own lean version of it. Since the PreDecorationFilter is tightly
coupled to the ProxyRouteLocator we also have to use our own stripped down version.

closes #123

Streamline the Hazelcast support with boot 1.3 and support storing events in hazelcast

closes #113

remove logfileEndpoint
rename logback.xml to logback-spring.xml in samples

fixes #98