[request] support for java.time

[IARI]

I is my understanding that java.util.Date should not be used anymore.
I suggest to add support for java.time.

[bdemers]

This will likely be added in v1. The current version of JJWT currently targets Java 7 APIs for Android compatibility (which is why we are still using Date)

I don’t know if I would say, ‘Date’ shouldn’t be used, but I would still much rather use Instant and Duration instead 😀

[lhazlewood]

Internal note: see #308 and #352

[limbic-derek]

Any updates on this? Seems like a smart API update to me.

[linghengqian]

Any updates on this? Seems like a smart API update to me.

This should be one of the milestones of 1.0, and judging from the issue distribution 1.0 is still heavy work. At the same time, the 0.11.3 and 0.12.0 milestones still have unresolved issues.

[bdemers]

@linghengqian the biggest thing in v1, is the JWE work, if you are interested in helping try it out, please take a look at the jwe branch 😄

[linghengqian]

@linghengqian the biggest thing in v1, is the JWE work, if you are interested in helping try it out, please take a look at the jwe branch 😄

I feel do not know how to start, for the vast and corresponding PR look it at the end stage, but does not have an issue of what it needs other parts (if I do not understand the function of snoatype-lift wrong, refer to #279 ).

[lhazlewood]

@linghengqian that's true - JWE is large and almost finished, so given the scope, it's probably best to leave the remaining work for JJWT team members. Normally I feel otherwise (anyone should jump in!) but it's a daunting task for jwe to wrap up because it includes so much stuff, like JWK support, key management algorithms, AEAD encryption algorithms, and various interface cleanup additions.

[lhazlewood]

Closing as duplicate of #235 so we can track this in one place