[
https://issues.apache.org/jira/browse/BEAM-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052158#comment-17052158
]
Ismaël Mejía commented on BEAM-5530:
------------------------------------
We can start to provide alternative methods for all of time uses of
`sdks/java/core` based on java time as a path towards removal. This way we can
then then start deprecating the Joda Time methods. WDYT ?
Extra comment I suppose we should map then internally towards Joda to avoid
breaking backwards compatibility for the Coders, is this correct [~lcwik] or
can we avoid that part?
> Migrate to java.time lib instead of joda-time
> ---------------------------------------------
>
> Key: BEAM-5530
> URL: https://issues.apache.org/jira/browse/BEAM-5530
> Project: Beam
> Issue Type: Improvement
> Components: dependencies, sdk-java-core
> Reporter: Alexey Romanenko
> Priority: Major
> Fix For: 3.0.0
>
>
> Joda-time has been used till moving to Java 8. For now, these two time
> libraries are used together. It will make sense finally to move everywhere to
> only one lib - *java.time* - as a standard Java time library (see mail list
> discussion:
> [https://lists.apache.org/thread.html/b10f6f9daed44f5fa65e315a44b68b2f57c3e80225f5d549b84918af@%3Cdev.beam.apache.org%3E]).
>
> Since this migration will introduce breaking API changes, then we should
> address it to 3.0 release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
