Setup asdf and direnv managed development environment

[iilyak]

Now cd into the project directory would activate correct versions of build dependencies.

Sorry for cleaning up the trailing spaces in README.md. My editor does that by default.

[tonysun83]

Seems test cases are having issues connecting with clouseau during mvn test phase:

java.net.ConnectException: Connection refused
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:741)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:401)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:370)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:292)
    at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
    at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44)
    at overlock.threadpool.ErrorLoggedThread.run(NamedThreadFactory.scala:40)

[iilyak]

@pgj Would it negatively impact your work on CI if I merge it?

[pgj]

@pgj Would it negatively impact your work on CI if I merge it?

No, I do not think so.

Running Clouseau in the CouchDB CI (and the respective developer setup) is supported through the releases section of this repository, i.e. downloading and unpacking pre-built JARs. It does not have to deal with the compilation. This makes launching the Clouseau nodes faster, can work with JRE 8, depends on the JRE itself, in exchange for not being able to serve development versions from the source locally. For that, one has to launch Clouseau as suggested in this PR for example, and separately run CouchDB configured for looking for clouseauN.