closes #321

Annotating the applicationRouteLocator bean with
@ConfigurationProperties yields the wrong configuration metadata.
Instead do a explicit properties bean to get correct metadata.

fixes #309

This CompositeRouteLocator allows extensions to add custom RouteLocators

To easily add new mvc controllers (e.g. from extensions) a new
annotation `@AdminController` is added.

 * Since the hystrix.stream incorrectly handles HEAD requests we had to change
   the detection for the hystrix-endpoint to a GET request.
   Issue https://github.com/Netflix/Hystrix/issues/1369

 * We need to improve Zuul's SimpleHostRoutingFilter and SendResponseFilter to
   close the underlying socket when an error occurs when writing the response.
   I hope that the code can be removen when my PR gets merged.
   Issue https://github.com/spring-cloud/spring-cloud-netflix/pull/1372

Fixes #290

With the fix for #260 we ignored all events from child contexts which turns out
to be wrong since the "main" application context is, in case spring cloud config
is used, is a child  of the bootstrap context. So we just act on the events from
WebApplicationContexts. After they're fired up the needed port information is
available.

fixes #277

With this change the AbstractNotifier isn't specialized on status changes, but
the default behaviour for the existing notifiers isn't changed.
In addition the existing notifiers have been improved so that subclassing has
become easier.
To have existing notifiers acting on other events you need to override
shouldNotify().

fixes #270

When includeing spring-cloud-netflix-hystrix-amqp to your application it looks
like that the ApplicationReadyEvent is fired twice (from main and child
application context). So we need to take care that only the events from the
main applications are taken into account.

fixes #260

Remove the activiti endpoint from the default set of proxified endpoints.
This aligns with the non present defaults for hystrix.

As it turns out (rather obvious) that the ThreadPools for registration and
status updating needs to be destroyed on application shutdown so that the
worker threads gets cancelled. To achieve this we simply register the
ThreadPools as spring beans (since they are implementing DisposableBean).

fixes #253

Fix the usage of RestTemplateBuilders which wasn't covered by PR #247

When having registered some applications via discovery and some via http you
can now add the appication names of the non-discovery to the ignored services
so that they won't considered as stale an be removed from the registry by the
ApplicationDiscoveryListener.

fixes #244

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

Since a HEAD request to the heapdump triggers a dump we need to test the
availability of the heapdump endppoint via OPTIONS-request.
To get this working we need to ensure that the OPTIONS-request are dispatched
to the zuul servlet as this wasn't done prio to this commit adding the
OptionsDispatchingZuulController.

Detecect endpoints by making a HEAD request instead of querying the configprops
since it is broken when having a second applicationContext

fixes #226

Sometimes Eureka only provides only the securedhealthUrl for the service.
Previous to this commit the applciation won't be registered in that case. So
with this commit the securedHealthUrl from Eureka is used, when available

fixes #224

Checks the DiscoveryClient's services on each heartbeat and removes all
services, which are no longer registered.

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

Adds an application view that displays a list of
Liquibase migrations as retrieved from the /liquibase Actuator
endpoint. The module is conditional on this endpoint being
available.

Adds an application view that displays a table of
Flyway migrations as retrieved from the /flyway Actuator
endpoint. The module is conditional on this endpoint being
available.

Fixes gh-206

fixes #209

closes #201

fixes #202

With this commit the icons from FontAwesome are used. To achive this the
webpack css-loader is used and the location for the module.css has slightly
changed.
Also I removed the ugly sidebar (what a short life) and added a slim navbar at
the top for the detail views.

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.

 - Updated Angular to 1.5.3
 - Removed Angular UI Bootstrap, to make the Angular update possible without
   updating Bootstrap
 - Moved every view into its own module
 - Added concatenation of the module js and css assets to the webserver
 - Created directives/components for the various visual components and trimmed
   down the controllers
 - Removed unecessary ngRoute
 - Removed classpath section in details (it is included in environment)
 - Moved the counters and gauges to a separated metrics view
 - Added target="_blank" for the logfile
 - Added information about version, loaded ui modules to the about page
 - Extracted the activiti view to a separate maven artifact

With this commit it is now possible to add your own ui modules to the servers
classpath and they will show up in the ui.
Every module needs an "entry" script file in the classpath located under
`META-INF/spring-boot-admin-server-ui/<modulename>/module.js`.
The module is be implemented as angular module and needs to be added to
the global `uiModules` list.
The spring-boot-admin-server-ui-activiti module is a simple sample for
adding a application view but it is also possible to add main-views.
Please have a look at the events module in spring-boot-admin-server-ui/modules.

Please note that the internals of the ui can change anytime.

From Spring Cloud Brixton on, the PreDecorationFilter doesn't pass sensitive
headers downstream.
So the ZuulProperties from the ApplicationContext needs to be used (instead
of creating a new instance), so that the properties can be customized.