[
https://issues.apache.org/jira/browse/IO-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570196#action_12570196
]
Niall Pemberton commented on IO-118:
------------------------------------
I don't see the point of this now since deleteQuietly was introduced in 1.4 -
why break compatibility on forceDelete to make it work like deleteQuietly -
when people can just use deleteQuietly? Seems to me like we now provide two
good options with both forceDelete() and deleteQuietly() for whatever people
prefer - either return a boolean or throw an exception.
I think this ticket just predated deleteQuietly() (IO-135) and we should now
close it as WONT FIX.
> Change forceDelete API to return the boolean success
> ----------------------------------------------------
>
> Key: IO-118
> URL: https://issues.apache.org/jira/browse/IO-118
> Project: Commons IO
> Issue Type: Improvement
> Affects Versions: 1.3.1
> Reporter: Henri Yandell
> Fix For: 2.x
>
>
> (Though I imagine it'll be 2.0 for API versioning, but reporting anyway).
> Would be nice to return the boolean that the delete method returns in
> forceDelete.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
