Shantanu Kumar

AFAIK support for SNI requires Java 8, and (based on the arguments I've seen) making that a requirement would leave many Java 6/7 users out. Linking old issues on this...

If there was a choice of using Text title instead of icons for the sections, the title could have been used to accommodate the unread count, e.g. `Home (236)`, `Mentions...

> I will probably upgrade this, but note that any dependency added by lein-ring can be superseded by depending on the thing explicitly I tried adding an explicit `tools.nrepl` dependency...

Currently, I'm working around this issue by creating a file `test/jetty-logging.properties` with the following content: ```properties org.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog ``` This forces Jetty to log to STDERR, without initializing any other logging.

I deploy a simple uberjar, where the main class 1. reads config file 2. uses some of the config to initialize SLF4j/Logback 3. loads rest of the application that logs...

@MichaelBlume I use lein-ring only during development. For production, I create the uberjar using `lein uberjar` with my own AOT main class/namespace.

Yes, that's right. I see the problem only at development time.

In this case I would expect the web server to abort with an error message, not due to port number collision but because the web server failed to bind server...

I found the error with lein-ring `0.9.7`, but I verified it occurs in `0.10.0` too. For me the error happens as I reported even when I change the port numbers...

Lein `2.7.1` on Oracle JDK 1.8, OSX.