Several classes are unnecessary about mango

[cjnolet]

ObjectMapperContext is used by a couple of the utility classes (in static code blocks) so they can register their mixins. I believe this is the case with both the types and the criteria in mango. We should make sure no functionality is lost if we remove this.

ByteArray was just a simple class Roshan added to make his life easier.

I'm okay removing the ValueRange stuff but I'd like it if we could still demonstrate a way to note a beginning and end ip address. Does Guava provide this?

Okay with Removing DateTimeUtils.

[eawagner]

I have already fixed the ObjectMapperContext in the Remove Mutable Static pull request.

I understand about ByteArray. Commons collections have a ArrayByteList which does the same things and implements the collections interface though.

Yes Guava has a way to represent any type as a Range as long as its comparable. I am going to leave this here for now though because it is being used in RangeStore and it would be a hassle to change.

DateTimeUtils is gone then.