jjwt-gson cannot use the require series methods of io.jsonwebtoken.JwtParserBuilder normally

[linghengqian]

Describe the bug
A clear and concise description of what the bug is.

• jjwt-gson cannot use the require series methods of io.jsonwebtoken.JwtParserBuilder normally.
• Found at Add support for io.jsonwebtoken:jjwt-*:0.11.5 oracle/graalvm-reachability-metadata#116 and Some plan to write additional unit tests for the class library need GraalVM Reachability Metadata linghengqian/graalvm-trace-metadata-smoketest#1 .

To Reproduce
Steps to reproduce the behavior:

• The git repository is located at https://github.com/linghengqian/jjwt-gson-ex-test .
• Execute the following steps to find the exception.

git clone [email protected]:linghengqian/jjwt-gson-ex-test.git
sdk use java 22.3.r17-grl
./gradlew clean test

• jjwt-jackson and jjwt-orgjson do not have this problem.

Expected behavior
A clear and concise description of what you expected to happen.

• jjwt-gson can use the require series methods of io.jsonwebtoken.JwtParserBuilder normally.

Screenshots
If applicable, add screenshots to help explain your problem.

• 

[lhazlewood]

Thank you for reporting this, we'll take a look after the JWE release!

[lhazlewood]

@linghengqian do you think this would be resolved via #771 ? That would be my guess. GSON number deserialization is terrible.

[linghengqian]

@linghengqian do you think this would be resolved via #771 ? That would be my guess. GSON number deserialization is terrible.

• @lhazlewood Adopting provide an enum that indicates the 'level' of precision desired scenario may not be something that should be on the 0.12.0 milestone. This kind of proposal looks like something that a major version milestone like 1.0.0 should have.

• Personally, I think we should use a custom ToNumberStrategy directly inside jjwt .