When the jolokia endpoint is missing the jmx section is hidden
additionally when the logging endpoint is also missing the logging
section is hidden too.

closes #398

For easier cusotmization. E.g. converting some of the data fechted
from the /info endpoint or to filter it.

For smaller screens (< 992px) the info is hidden from the application
list. Also the Status and the actions buttons are now shown on two
lines, so that longer statuses don't overlap with the buttons.

fixes #394

Apparently we need some getters so that the metadata for the
configuration properties is generated.

fixes #391

fixes #395

fixes #387

closes #386

My PR spring-cloud/spring-cloud-netflix#1448 has been merged into
Dalston, therefore we can remove our implementation and need to fix some
comile issues.

fixes #382

With this commit you can use simple patterns to match services to
ignore.
A pattern can look like this "foo*", "*foo", "foo*bar".

closes #377

Wooohoo!

With this commit the ignoreErrors=true is set for non-modifying
operations as search, list and read.

fixes #374

With this commit you can specify either a URL or a serviceId for the
Turbine server location.
Note that `spring.boot.admin.turbin.url` is replaced by
`spring.boot.admin.turbine.location`.

closes #373

The format for /liquibase and /flyway has changed with Spring Boot 1.5.0
to support multiple Flyway/Liquibase beans. With this change we adpot
the new format, but also support the old one.

closes #371

The info is now fetched by the server on status change. This way the
info can be used in the notifications and also improves performance when
listing a huge amount of applications in the ui.

closes #349

Make the webpackconfig handle windows paths correctly.

fixes #363

Add a section on getting help and removed the stackoverflow badge since very often it doesn't render.

Added documentation and a sample on how to secure the SBA-Server and
leverage the new login ui-module

closes #361

This new ui-module provides a login page and a logout button.

closes #361

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.