New configuration for Guava Range default bound type.

[jorool]

Now it's possible do set a default bound type for Guava Range objects.
The intent of this is to get the JSON deserialized without informing the bound types every time even when wanted to use the same one for all objects.
The configured default bound type is passed to the deserializer by constructor method.
If the JSON object has no bound type and there's no default configured, we still get the exception.
I added some test cases with and without default bound type configured.

[jorool]

@cowtowncoder What about that failing test?

TestVersions.testMapperVersions:16->assertVersion:35 expected:<2.6.2-SNAPSHOT> but was:<2.6.1>

[cowtowncoder]

@jorool I do not see any test failures. Message would indicate that you haven't done a clean Maven build perhaps? ("mvn clean compile")

[jorool]

@cowtowncoder I'm talking about Travis CI. The "check" failed. 😄

[cowtowncoder]

Hmmh. That's odd, but reliability of Travis setup has been rather poor. :-(

[jorool]

@cowtowncoder So... what should we do? Will you merge it?

[cowtowncoder]

Yes, I think that's good enough.

One thing first however: unless I have asked about it already... we need filled in Contributor License Agreement (https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf) before the first merger contribution. This is only needed once, and after that we can accept any number of contributions for Jackson projects.

The easiest way is usually to print CLA form, fill & sign, scan and email to info at fasterxml dot com.
Once we receive it I can go ahead and merge this. It will be a good addition.

Thank you in advance.

[jorool]

@cowtowncoder Done. Email sent.

Let me know if you need something else.

Thanks.

[cowtowncoder]

Ok this caused the bug -- PackageVersion must not come from version of another module, like jackson-databind.
It is generated by Maven build. I removed this which fixes the unit test fail.