-
-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update rule 2.11 to discourage use of joda-time in favour of java.time #44
Comments
indeed! +1 |
Sure. Any of you up for a PR? |
Sure :)
…On Tue, 6 Jun 2017, 20:51 Alexandru Nedelcu, ***@***.***> wrote:
Sure. Any of you up for a PR?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEsiuq6gYQUl7L9ZwaJCfMFs82Txbm08ks5sBa2lgaJpZM4NxTIp>
.
|
jjst
added a commit
to jjst/scala-best-practices
that referenced
this issue
Jun 7, 2017
jjst
added a commit
to jjst/scala-best-practices
that referenced
this issue
Jun 7, 2017
alexandru
added a commit
that referenced
this issue
Jun 12, 2017
2.11: Favour java.time over joda-time ⌚ (fixes #44)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rule 2.11 states:
JSR-310 has now been implemented as Java 8's new java.time API and even jodatime's website is asking users to migrate:
As Java 8 has become more and more common, it's probably time to deemphasise joda-time and recommend the java.time API as the standard approach, with joda-time as a fallback for people stuck in pre-Java 8 land.
The text was updated successfully, but these errors were encountered: