Reworking indexes
Crazy generic type inference stuff
Last changes
Streamlined RiakIndex usage

The user no longer has access to instantiate RiakIndex implementations directly.
Instead, they are completely managed by the RiakIndexes container.
Tidying up, Javadoc, unit tests
Javadoc updates to RiakObject
Unit testing for RiakIndex classes
Added RiakIndex tests and fixed off by 1 error
MOAR JAVADOC

Made all the titles pretty, added the package javadoc
Merge branch 'improved-index-api' of github.com:basho/riak-java-client into improved-index-api
One last change to Javadoc. Honest.
Relocated typeFromFullname to IndexType

adjusted tests accordingly
Merge pull request #272 from basho/improved-index-api

Improved index api
Embrace the delete key

Reworked internals to drop multi-protocol support as it is no longer needed.
Merge pull request #273 from basho/core-improvements

Embrace the delete key
Moved to Nett 4.0.7-final

We'd been working off Beta3 and a number of things had changed
since then. This updates the dependency to 4.0.7 final and
makes the necessary changes in our code.
Bug fix, multiple expections from pipeline

Forgot to change this. It would throw a NoSuchElementException if
the timeout handler had already been removed.
Merge pull request #274 from basho/update-to-netty-4-final

Moved to Netty 4.0.7-final
Combined ConnectionPool and RiakNode

The two classes were inherently coupled after removing simultaneous,
multiple protocol support; You can't have a RiakNode without
a ConnectionPool and the ConnectionPool isn't used outside of a RiakNode.

In addition, having them as two classes created an abstraction layer that
added complexity and made a couple things clunky - notablly registering the RiakNode as a listener
to a specific channel handler in the pipeline.

I moved and modified all the ConnectionPool tests to operate on the RiakNode.
Fixed compiler warnings.

The raw typing was causing compiler warnings.