commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
Date Thu, 17 Oct 2013 08:02:46 GMT

    [ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797699#comment-13797699
] 

Joerg Schaible commented on LANG-769:
-------------------------------------

bq. Should we move it into the exception subpackage?

That package was originally meant to collect stuff with functionality around exceptions, but
not to collect the various exceptions of lang. However, I failed myself, when I introduced
the CloneFailedException :-/

> Please restore NotImplementedException and UnhandledException
> -------------------------------------------------------------
>
>                 Key: LANG-769
>                 URL: https://issues.apache.org/jira/browse/LANG-769
>             Project: Commons Lang
>          Issue Type: Improvement
>          Components: lang.exception.*
>            Reporter: david cogen
>            Priority: Minor
>             Fix For: 3.2, Discussion
>
>
> Why were these removed? I found these very useful and used them often. As the version
2.6 api javadoc states, "This exception supplements the standard exception classes by providing
a more semantically rich description of the problem."
> Just want you to realize that these have found direct use outside the library; not just
internal use within commons-lang.
> I will define these missing classes myself, or maybe include both commons-lang and commons-lang3
(but I really don't to do that). It would be very nice to have these back.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message