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.

With this commit you can specify the management.port for a discovered service
via the metadatamap.

With this commit you can from now on register the application on multiple
servers. You need to set spring.boot.admin.register-once to false and
assign a list of urls to spring.boot.admin.url

fixes #205

Use the metadata for health-/managament-url in the default service conversion.
This allows custom health- and management-path per application.

fixes #205

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.

Update to Spring Cloud Brixton and add the concept of ServiceInstanceConverters.
A ServiceConverter is used to convert discovered ServiceInstances to
Applications. The old converter and one for Eureka is provided. It is also
possible to provide your own implementation.

closes #154

This commit contains multiple changes:
 - Start the registration task after the ApplicationReady event. This makes
   AdminClientProperties.isReady() unnecessary.
 - The RegistarApplicationListener has two new public methods to start/stop the
   periodic registration task.
 - Add spring.boot.admin.auto-registration property (default: true). When this
   property is set the registration task is automatically scheduled after the
   ApplicationReadyEvent.

closes #151

The RemindingNotifier sends periodic notifications using a delegate. It must be
added explicitly to the ApplicationContext

In case prefer-ip is true and no server.address is set use the IP address from
InetAddress.getLocalHost(); like it is done in Eureka.

Add spring.boot.admin.client.enabled property to explicitly disable the
spring-boot-admin-client, (e.g. for unit tests). Defaults to true. The client is
active when spring.boot.admin.client.enabled is true and spring.boot.admin.url
is set.

fixes #156

In case you have clustered admin servers, you can now specify multiple urls for
the client to register at. So that in the case the first server is down it will
register at the next one specified in the list. This allows you to do cluster-
ing without the need for a load-balanced host.

Cause it was often requested, now the context-path for the admin server is
configurable. This allows to move the admin-ui and endpoints to other http-
paths than "/".
NOTE: I'd still advise not to add the admin to the application you want to
monitor.

For less commits to the gh-pages remove the last-update-label from the footer.
So that a commit is only made if the content changes.

Take the servlet-path into account when computing the management-/healht-url.
This is not done for the service-url, since the main use-case for setting the
servlet-path is to get the dispatcher-servlet out of the way for other servlets.

fixes #133