[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13854000#comment-13854000 ] Benedikt Ritter commented on LANG-769: -- What about UnhandledException? Do we want to add it or can we close this ticket for 3.2? 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 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.4#6159)
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13854802#comment-13854802 ] Henri Yandell commented on LANG-769: Not enough support for UnhandledException. Issue already closed. 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 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.4#6159)
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13835994#comment-13835994 ] Pavel Bekkerman commented on LANG-769: -- Great having it back. In which version to expect this? 3.1 - the last one I see - doesn't have it. 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 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)
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13836056#comment-13836056 ] Gary Gregory commented on LANG-769: --- It should be in the next release, which is unscheduled at the moment. 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 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)
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801099#comment-13801099 ] Henri Yandell commented on LANG-769: They're all runtime exceptions, so I'm not sure it matters too much. I've put this in the core package for shortness sake. svn ci -m Returning NotImplementedException to Lang after it was removed in Lang 3.0 per the request in LANG-769. src Adding src/main/java/org/apache/commons/lang3/NotImplementedException.java Adding src/test/java/org/apache/commons/lang3/NotImplementedExceptionTest.java Transmitting file data .. Committed revision 1534380. 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 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)
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797697#comment-13797697 ] Henri Yandell commented on LANG-769: I'm in favour of the NotImplemented one too. I'll admit to it always being my favourite as well. Baby, bathwater etc :) I like the positive approach too, but for the sake of migration I'm tempted to stay with the old name. Plus that way it does support both not yet and not ever. Adding another argument for an issue ID (effectively error code, but a positive one) is good. Should we move it into the exception subpackage? 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)
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[
https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482164#comment-13482164 ] Joerg Schaible commented on LANG-769: - ... and what does it actually help the client to know the difference? ;-) 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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482206#comment-13482206 ] Steve Gillam commented on LANG-769: --- All the difference in the world - 'NotImplemented' is typically static and nothing YOU can do will change it, 'Unsupported' is typically state driven (e.g driveBicycle(fish)). My client wants to know the difference (esp. during rapid TDD): 'Unsupported': I think you've been silly 'NotImplemented': come back later or go shout at somebody. 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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482367#comment-13482367 ] Charles Honton commented on LANG-769: - Joshua Bloch's Item 60: Favor the use of standard exceptions (From Effective Java) is appropriate here. I recommend using java.lang.UnsupportedOperationException and java.lang.IllegalStateException. If you need additional context, use a constructor that sets the detail message. 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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482555#comment-13482555 ] Steve Gillam commented on LANG-769: --- If we're down to quoting design principles G. Booch is God: An abstraction denotes the essential characteristics of an object that distinguish it from all other kinds of object and thus provide crisply defined conceptual boundaries, relative to the perspective of the viewer. (Object-Oriented Design With Applications, Benjamin/Cummings, Menlo Park, California, 1991.) Exception(NullPointer) (and synonyms) - NullPointerException UnSupportedOperationException(NotImplemented) (and synonyms) - NotImplementedException Is it an abstraction relevant to the community at large? Not counting those in this thread... .Net, IBM, Google, NetBeans, JBoss, Mozilla...(gave up counting) 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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[
https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482567#comment-13482567
]
Gary Gregory commented on LANG-769:
---
I can see that there can be a subtle difference between
{{NotImplementedException}} and {{UnsupportedOperationException}}, so I am in
favor of adding NotImplementedException back, which could also be named
{{UnimplementedException }}
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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[
https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482741#comment-13482741
]
Steve Gillam commented on LANG-769:
---
Disambiguation/Accuracy of the semantic (and, thus, its name) is key here -
otherwise it will quickly lose it's worth and become a valid candidate for
disappearing again (as any such should be).
Whilst Not(Un)Implemented is the most often created it does not communicate the
semantic well and could well be confused with the permanent decision not to
implement an optionalAPI call.
It somehow needs to represent itself (and, thus, the response (human/systemic)
as being a function of the development lifecycle ('You told me you'd
finished!'). Perhaps others cleverer than I can propose a succinct
representation?
Obviously it needs to be a subclass of RuntimeException so we don't have to run
around polluting 'completed' code with throws clauses :)
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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[
https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482875#comment-13482875
]
Gary Gregory commented on LANG-769:
---
Interesting, NotImplementedException could mean, not yet or not ever. So
expressing the intention in the positive could help: {{ToDoException}},
{{ToBeImplementedException}}, and the like. I could see usage like {{throw new
ToDoException(LANG-987);}}
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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13481477#comment-13481477 ] Charles Honton commented on LANG-769: - What's the semantic difference between NotImplementedException and java.lang.UnsupportedOperationException? 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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482036#comment-13482036 ] Sebb commented on LANG-769: --- The Javadoc for UnsupportedOperationException says: bq. Thrown to indicate that the requested operation is not supported. It does not imply that the operation cannot be implemented. 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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13480710#comment-13480710 ] Steve Gillam commented on LANG-769: --- no clear criteria as to which semantically rich description should be there and which shouldn't - admit there is little distinction between the two but one of them should be. Or is it that 'without any clear criteria as to which semantically rich descriptions' are missing we won't add 'any'? (this could be said of any item within commons-lang(3) - if you disregard the argument 'because people want/use it'). 'net searches reveal many patterns where a 'NotImplemented' semantic is useful with no apparent supplier in the standard JDK - presumably hence its (ex)presence in commons-lang. One such pattern (beefing up the 'because it's needed' criteria) is to systematize ignoring (via assumeException(...)) of developed (ie. not @Ignore'd) test/src/java/* test cases where some aspect of that test's implementation (movable as development progresses) throws NotImplementedException in main/src/java/* As it is I'm having to utilise commons-lang 2.4 (as use other commons-lang goodies and frustrated that can't just bring in latest version) 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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13480743#comment-13480743 ] Matt Benson commented on LANG-769: -- Well, it's perhaps not the tidiest situation, but [lang] v3 was repackaged and re-classified (i.e. Maven groupId) for the express _purpose_ of allowing it to live alongside v2.x on a given classpath. You therefore _can_ just bring in the latest version, FWIW. 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
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260518#comment-13260518 ] Jean-Noel Rouvignac commented on LANG-769: -- Hi Henri, I agree with David Cogen: these exceptions are the ones I use most! I am using NotImplementedException to fail fast in case I did not handle a specific path in the code when I deemed it unnecessary to handle from the start or when could not foresee changes coming in, like a newly added values to an enum for example. Then I am using UnhandledException to bypass the horrid checked exception in Java which is needed just about all the time. Please add them back, I miss them so much! Thanks, Jean-Noel Please restore NotImplementedException and UnhandledException - Key: LANG-769 URL: https://issues.apache.org/jira/browse/LANG-769 Project: Commons Lang Issue Type: Improvement 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13156555#comment-13156555 ] Henri Yandell commented on LANG-769: Fair point on the without warning - they were removed from 3.0 before 2.5 was released, but that wasn't how it subsequently looks. Should have been deprecated in 2.5 and 2.6 along with the other removed items. The reason for removing is that there is no clear criteria as to which semantically rich description should be there and which shouldn't. Too many exception implementations without much value. Please restore NotImplementedException and UnhandledException - Key: LANG-769 URL: https://issues.apache.org/jira/browse/LANG-769 Project: Commons Lang Issue Type: Improvement 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (LANG-769) Please restore NotImplementedException and UnhandledException
[ https://issues.apache.org/jira/browse/LANG-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13149772#comment-13149772 ] david cogen commented on LANG-769: -- Forgot to add: At the very least, these should have been deprecated rather than just removing them without warning. But as I said before, these are generally useful and I'd love to have them back. Please restore NotImplementedException and UnhandledException - Key: LANG-769 URL: https://issues.apache.org/jira/browse/LANG-769 Project: Commons Lang Issue Type: Improvement 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
