Spring Cloud Brixton hasn't been released yet, so to get the Spring Boot Admin
release out. We downgrade to Spring Cloud Angel.SR3.

In cas a pull request is tested, the secret environment variables are not
present, because they could be exposed by a malicious pull request. So we can
only decrypt the gpg-keys only when the keyphrase is availible.

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

To not pollute the log with warnings when an app is offline log the exception with
debug when the application status already was offline before the check. So only the
first exception when the state changes to offline will be logged.

closes #125

Since the build errors when a before_install script fails when the exitcode is non-zero we
have to use bashs regular if-then-else syntax to return a zero exitcode when $TRAVIS_TAG is not set.

Add an encrypted GnuPG keyring and use it for signing the artifacts.
When a Tag is present deploy to sonatype staging repository.

Tests in Abstract*.class are not executed during the maven build, so I moved
the tests for code in AbstractNotifierTest to MailNotifierTest

To not accidentally expose senstive urls only expose whitelisted
management-endpoints via the zuul proxy filter.

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

/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

Add hint to the snapshot builds made with every travis build and fix some typos

Check if the status field is a String and don't propagate any Exception
from the StatusUpdater, so that the application don't fail like in #120

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

closes #113

Due to our use of @Conditionals on our @Configuration-classes the import must be deferred, so that the classes are processed after all other @Configuration-classes

By using local.server.port, local.managment.port and ApplicationReadyEvent the port detection and ready state detection can be simplyfied in boot 1.3