Will Sargent

The issue may be specific to Logback, which creates a timestamp for logging that uses System.currentTimeMillis, meaning that it's only accurate to the millisecond. If you have several requests inside...

It's a Logback best practice, even: > In order to release the resources used by logback-classic, it is always a good idea to stop the logback context. Stopping the context...

It looks like the sbt-native-packager already deals with the PID issue mentioned ``` // Since play uses separate pidfile we have to provide it with a proper path // name...

Also https://medium.com/jeroen-rosenberg/lightweight-docker-containers-for-scala-apps-11b99cf1a666

You can bind a standalone client very simply, as it's a wrapper around `AsyncHttpClient`, which is exposed: https://github.com/playframework/playframework/blob/master/framework/src/play-ahc-ws/src/main/scala/play/api/libs/ws/ahc/AhcWSModule.scala#L207

You can also use `wsClient.underlying[AsyncHttpClient]` in a pinch and provide an implicit conversion to `StandaloneWSClient`. I'm not sure off the top of my head how much overhead is involved, but...

@domdorn Is this something you'd be able to contribute as a PR?

@domdorn I would suggest using https://github.com/sbt/junit-interface/ if possible, since that's what Play leverages

@hepin1989 are you volunteering?

@hepin1989 exactly, right now it's using play-doc. If you can map to Paradox, that would be a great start.