You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Suggestion: Replace use of joda-time with plain java time handling? #61
Hi, thanks for the suggestion! Indeed, newly created apps may want to get rid of the 3rd party dependency but I still want to keep backward-compatibility for a while. With that being said, this project will remove (or move the joda-time support to an optional module) when I get the confidence that most developers are happy with it in the future.
I forgot to mention this. This library already supports java.time.* classes by default. You still need to accept the unnecessary joda-time resolution but there is no blocker if you want to use java.time.* APIs instead.
Thanks for a conscious and nice reply! Our code scan analysis gives a warning on the current version having a CVE, which lead me into suggesting replacing it: https://nvd.nist.gov/vuln/detail/CVE-2024-23080
Activity
seratch commentedon Apr 12, 2024
Hi, thanks for the suggestion! Indeed, newly created apps may want to get rid of the 3rd party dependency but I still want to keep backward-compatibility for a while. With that being said, this project will remove (or move the joda-time support to an optional module) when I get the confidence that most developers are happy with it in the future.
seratch commentedon Apr 12, 2024
I forgot to mention this. This library already supports java.time.* classes by default. You still need to accept the unnecessary joda-time resolution but there is no blocker if you want to use java.time.* APIs instead.
madsop-nav commentedon Apr 17, 2024
Thanks for a conscious and nice reply! Our code scan analysis gives a warning on the current version having a CVE, which lead me into suggesting replacing it: https://nvd.nist.gov/vuln/detail/CVE-2024-23080