Issue#1252 Object to number strategy fix

[madhavjha-git]

By default GSON maps object to number in double format. Changed this default behavior by changing strategy to ToNumberPolicy.LONG_OR_DOUBLE. This will enable GSON to map objects to number properly. See #1252 for example.

[bartoszwalacik]

@madhavjha-git is this solution backward compatible? What happens if a new version on Javers deserializes data persisted by the previous versions?

[madhavjha-git]

@bartoszwalacik Yes . This issue only happens during deserialization. I saved data using previous version and I see data was saved properly in jv_snapshots.

"state": {
"data": {
"$numberLong": "99999999999"
},
"type": "number"
},

Only after calling findShadows we get

    {
        "type": "number",
        "data": 9.9999999999E10
    }

But after this objectToNumberStrategy change, it works fine.

[bartoszwalacik]

merged from here https://github.com/javers/javers/pull/1282/commits

[bartoszwalacik]

thanks @madhavjha-git , I will release it soon