Removing redundant close of client connection in test
Merge pull request #99 from NiteshKant/master

Fixing a flaky test.
Adding more debug info to the flaky test.

The test ConnectionPoolTest.testReuse() fails only on the cloudbees server and there does not seem to be anything wrong in the test as such.
The last run showed that the server was not able to close the connection when the test finished, as it was not even aware of the connection.
These debug logs will tell us if the tests are run in parallel or if there is some mismatch in expectations due to timing delays.
Merge pull request #102 from NiteshKant/master

Adding more debug info to the flaky test.
Fix for issue #100
Fix for issue #90

Added a basic HTML page dumping the error stack for the "catch-all" error handler.
Another attempt at finding & fixing a flaky test.

The last failure showed that the expectation of the test for the server to close the connection to trigger a close on the client was not met as the server was not aware of the connection at that point.

 Now, adding a write on the connection from the client to make sure the connection is completely established.
rx-netty contexts implementation.
Fix build failure

rxjava-0.18.1 removes all math related methods. Using rxjava-math instead.
Fix test failure

New rx-java version thrown NoSuchElementException from last() operator when there is no element.
Fixing groovy examples build failure
Merge branch 'master' of https://github.com/NiteshKant/RxNetty into contexts

Conflicts:
	rx-netty-remote-observable/build.gradle
	rx-netty-remote-observable/src/test/java/io/reactivex/netty/RemoteObservableTest.java