[
https://issues.apache.org/jira/browse/LANG-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926407#comment-17926407
]
Elliotte Rusty Harold commented on LANG-1763:
---------------------------------------------
If there is a 1:1 replacement, great, but there isn't always one. Sometimes
much more invasive changes are required. Occasionally methods are deprecated
without replacement because no one should be doing that, ever. I'm reminded of
Thread.suspend and Thread.stop, for instance.
> 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)