[
https://issues.apache.org/jira/browse/LANG-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926766#comment-17926766
]
Gilles Sadowski commented on LANG-1763:
---------------------------------------
bq. It's just that the replacement isn't a one-to-one drop-in where you change
a method name. The necessary functionality is available in the JDK but with a
different API
I believe that is what [~ggregory] dubbed "no replacement" (meaning: "You have
to recode it properly yourself", of course with the support of the JDK).
And that's the point for clarifying the implication on "dev", and the decision
(to deprecate) be taken there.
> Deprecate FastDateFormat
> ------------------------
>
> Key: LANG-1763
> URL: https://issues.apache.org/jira/browse/LANG-1763
> Project: Commons Lang
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Priority: Major
>
> FastDateFormat has bugs, is out of date, and solves a problem that no longer
> exists. That is, it's a thread-safe replacement for SimpleDateFormat. But
> SimpleDateFormat should be replaced by java.time classes in Java 1.8 and
> later, which are thread safe. So deprecate FastDateFormat with a suggestion
> that devs use java.time instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
