Les Hazlewood

Just a note - we'll probably need to hold off on any changes like this until we address #311, at which point the Clock interface (and others) may change. To...

Because of a backwards-incompatible breaking change, semver requires this to wait until at least `1.0.0`. Assigning that milestone and we'll deal with it at that time.

Just an update for those following along: The current plans around this issue is that we'll probably keep JDK 7 compatibility until *just* before we release 1.0 final. It'll be...

#178 is all that remains, and the current plans are to get the JWT team together in person to knock it out as soon as possible. Due to work commitments...

@DanFTRX correct, our 1.0 release will utilize JDK 8 APIs, but not JDK 9 or later. Also, our release just prior to 1.0 will really contain everything for the 1.0...

@DanFTRX it's a tough call - thankfully JJWT is quite stable, so other than 3rd-party dependency security issues - like Jackson recently - this may not be an issue at...

That's pretty slick! Odds are very high that we'd probably only use language features supported by desugaring, so hopefully we won't see any issues. I can't say for sure, but...

@DanFTRX thanks for the update, that's really helpful. I've made a *ton* of progress on JWE the last week, so hopefully it won't be too much longer before I can...

Yeah, I'm fixing that now (Open JDK 7 was core dumping when Cobertura was enabled). That said, I don't think the current implementation approach is the right way to go:...

Quite possibly - we'll double check since there seems to be more interest.