commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek E (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
Date Tue, 21 May 2013 17:03:17 GMT

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

Derek E commented on LANG-769:
------------------------------

I really like the idea of a ToDoException, though I would provide 2 constructors: one with
just a message and another that takes a message and issue ID.

{{throw new ToDoException("Doing TDD. Still need to handle this path.");}}

{{throw new ToDoException("Planned for Sprint 5", "LANG-769");}}
                
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message