1. 08 Jan, 2017 1 commit
  2. 15 Nov, 2016 1 commit
    • Detangle server from client · a99a889a
      Johannes Edmeier authored
      With this commits the server no longer depends on the client. The
      classes for the clients are moved to de.codecentric.boot.admin.client
      package.
      Since the perspective on applications is totally different from client
      and server the model has been split apart.
      
      What means this for users:
      1) The client is no longer a transitive dependency for your admin server
      you may need to add it explicitly to your dependencies, respectively
      jolokia-core in case you're using discovery and want to use the jmx-bean
      interface
      
      2)In case you have cutomised parts of the client you need to reflect the
      package change.
      
      fixes #332
  3. 10 Jul, 2016 1 commit
  4. 27 Apr, 2016 1 commit
    • Update to Brixton and add Eureka-Service converter · 272633e1
      Johannes Edmeier authored
      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
  5. 21 Oct, 2015 2 commits
    • rework hazelcast support · 8715d2c6
      Johannes Edmeier authored
      Streamline the Hazelcast support with boot 1.3 and support storing events in hazelcast
      
      closes #113
    • Use Spring 4.2 events & consistent formatting · 3f4da621
      Johannes Edmeier authored
       * Use @EventListener instead of ApplicationListener-interface
       * Don't inherit ClientApplicationEvent from ApplicationEvent - so JournaledEvent isn't needed anymore
       * added eclipse formatter rules
       * reformatted all files
  6. 30 May, 2015 1 commit
    • Added serverside health-checking. As prerequisite for mail-notification. · 0a931384
      Johannes Stelzer authored
      The health-check is made at a fixed interval (default: 10s) for all expired status-information (default-lifetime: 30s).
      The application health-endpoint must either respond with a JSON-Body having a status-field or with an empty body and all 2xx-http-responses are interpreted as UP and every other status as DOWN.
  7. 26 Apr, 2015 1 commit
  8. 18 Mar, 2015 1 commit
  9. 04 Mar, 2015 1 commit
  10. 25 Feb, 2015 1 commit
  11. 08 Dec, 2014 2 commits
  12. 17 Nov, 2014 1 commit
  13. 14 Nov, 2014 1 commit