[
https://issues.apache.org/jira/browse/LANG-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926401#comment-17926401
]
Gary D. Gregory commented on LANG-1763:
---------------------------------------
Saying "Use java.time" is not acceptable IMO, you have to say excalty which
class and which method should be used instead of ours in the deprecated comment
for each method.
If there is no replacement, then you have to say "Deprecated with no
replacement".
Anything less and you're sending users off to a wild goose chase.
> 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)
