You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Rui Wang (JIRA)" <ji...@apache.org> on 2018/10/01 21:31:00 UTC
[jira] [Commented] (BEAM-5530) Migrate to java.time lib instead of
joda-time
[ https://issues.apache.org/jira/browse/BEAM-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634661#comment-16634661 ]
Rui Wang commented on BEAM-5530:
--------------------------------
cc [~kenn], [~kedin], [~apilloud]
We might need to pay attention on this JIRA.
> 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
> 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
(v7.6.3#76005)