Fix int type transformed as BigDecimal value when parsing as Map

[ebuildy]

Using with Jackson2 parser, a simple parsing of { "data" : 1} gives a BigDecimal instead an integer. In my case, valueClass is Object, but the JSON current token is VALUE_NUMBER_INT not FLOAT.

I parse as a Map. No problem if I parse as a class with "int" type.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[ebuildy]

I signed it!

[googlebot]

CLAs look good, thanks!

[chingor13]

Thanks for submitting this and sorry for the delay in reviewing it. Can you add a unit test for this?

[sduskis]

@ebuildy, can you please add a unit test for this change?

[ebuildy]

Sure I will this week, thanks you.

[sduskis]

@ajaaym, this needs a unit test. Can you please get someone to resubmit this with a unit test?

[ajaaym]

@sduskis yes

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[pmakani]

@sduskis unit test added, PTAL.

[sduskis]

Please use IDE settings that do not use * but rather use individual imports.

[sduskis]

@pmakani, there are a lot of formatting changes here. Please raise a separate PR for just the formatting changes.

[pmakani]

@pmakani, there are a lot of formatting changes here. Please raise a separate PR for just the formatting changes.

PR #619

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

The comment was addressed.

[chingor13]

Turns out this behavior change is breaking a bunch of internal customers.