... since we use webpack.

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.

otherwise it gets mixed up whith the standard html title attribute

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

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.

fixes #184

fixes #175

Chrome dosesn't send parallel requests for the same url. To circumvent that
behavior add a dummy request-parameter to the event-stream url. Otherwise
the journal section shows no content on chrome while doing the sse long polling

If the management.port and server.port is not the same, the current logfile-
endpoint detection fails. With this commit the presence of the endpoint is
determined via a HEAD-request

fixes #165

When an empty application list was initially returned the events wasn't  pushed
into the applications array, because the Applications.query returned no array.
This issue made a page refresh necessary.

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

closes #137

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

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.

This should avoid confusion as in #131

Rather than relying on a constant mbean name for logbacks JMXConfigurator mbean, search for
all available beans of the type. If a single one is found take that. If multiple are found
first choose the one with Name=application name, if not present take the one with Name=default.
In case none matches display an error.

closes #124

closes #121

/info and /configprops are from now on only fetched in the overview on first render
and whenever the status of an application changes.

closes #95

But make no use of it.

fixes #96