If we run in to an error starting the system during development, we may
try to stop this component before it has started. This guards against
errors when doing that.
Upgrade to Jetty 11
This upgrades us to ring 1.11, which moves from Jetty 9 to Jetty 11.
This includes using a fork of cognitect's http-client that works with
Jetty 11's client impl.
Directly depend on slf4j-api
This is a bit of a mystery: if we let slf4j-api come in via a transitive
dependency, our logback.xml file is ignored (at least in dev & test), so
all logging goes to stdout. clojure.tools.logging is finding slj4j-api
in both cases, but logback does not get initialized in the case where
this isn't a top-level dep.
I have no idea why this is happening! Logging is terrible.
Make event component more resilient
If we run in to an error starting the system during development, we may try to stop this component before it has started. This guards against errors when doing that.
Upgrade to Jetty 11
This upgrades us to ring 1.11, which moves from Jetty 9 to Jetty 11. This includes using a fork of cognitect's http-client that works with Jetty 11's client impl.
Directly depend on slf4j-api
This is a bit of a mystery: if we let slf4j-api come in via a transitive dependency, our logback.xml file is ignored (at least in dev & test), so all logging goes to stdout. clojure.tools.logging is finding slj4j-api in both cases, but logback does not get initialized in the case where this isn't a top-level dep.
I have no idea why this is happening! Logging is terrible.