[
https://issues.apache.org/jira/browse/IO-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232967#comment-14232967
]
Gary Gregory edited comment on IO-462 at 12/3/14 12:53 PM:
-----------------------------------------------------------
(0) Good call to deprecate.
(1) Do we need to worry about breaking the behavior of apps that catch
{{IOExceptionWithCause}} in a non-major release?
(2) It might not even be worth reimplementing {{IOExceptionWithCause}} as a
"clean" {{IOException}}.
was (Author: garydgregory):
(0) Good call to deprecate.
(1) Do we need to worry about breaking the behavior of app that catch
{{IOExceptionWithCause}} in a non-major release?
(2) It might not even be worth reimplementing {{IOExceptionWithCause}} as a
"clean" {{IOException}}.
> IOExceptionWithCause no longer needed
> -------------------------------------
>
> Key: IO-462
> URL: https://issues.apache.org/jira/browse/IO-462
> Project: Commons IO
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Sebb
> Priority: Minor
>
> The class IOExceptionWithCause is no longer needed in Java 6, because
> IOException now includes a constructor that takes a Throwable.
> The class should be deprecated and internal usage can revert to using
> IOException directly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
