doc update thanks to @dkuppitz and retain() addition.
Add test for validating that session requests with bindings are preserved between requests.
Expand the test for keeping bindings across requests a little bit.
add biXXx lambda test cases.
updated a label test in HasTest to use modern now. minor nothing. about to do something crazy.
some crazy things here --- you can now register the GraphComputer with steps so that steps can determine the most efficient way to execute their behavior based on the features of the GraphComputer. This was initial done by having numerous types of XXXStep -- SelectStep, SelectOneStep, SelectComptuerStep, SelectOneComputerStep. This is not good. Now there is simply SelectStep which implements AnalyzesGraphComputer and now Strategy or multiple steps required. I need to think through the ramifications as now strategy work is sort of split in two places.....
Add test for ensuring that NoSuchElementException does not popup for Traversal iteration.
Globally add Override annotation.
Modify the grateful dead graph to use label instead of type property for vertices #110

Also consider #112 as *-vertices files are now also in gremlin-test.
Update changelog.
minor nothings.
unfold(), like scatter() before it, unrolls Maps into a stream of Map.Entry objects.
Auto-rollback if the session dies and a transaction is still open #109

This prevents transactions from hanging about in some random thread somewhere after a session is ended and the client doesn't properly close the transaction.
Merge remote-tracking branch 'origin/master'
Update changelog.
Rename tests for consistency sake.
FoldStep now takes a Traverser<S>  in line with the new model that lambdas get access to Traveser.
there is now a GraphComputerStrategey that registers with each step that is EngineDepdenent whether its running on GraphComputer or not. This is important cause now we can have one step and it can decide which algorithm to execute depending on its engine --- e.g. no more JumpStep and JumpComputerStep. All I need to get rid of now is CountCapStep and there is nothing inherently special about GraphComputer.
Improve the ClusterAware interfaces.
Clean up javadoc.