Github user gzak commented on the pull request:
https://github.com/apache/commons-lang/pull/98#issuecomment-113787062
Why though? If you're using one of those methods, you're essentially saying
"I don't care about this error, just raise it to the top-level handler". At the
top, you generally just catch Throwables and log the error without actually
doing anything (presumably, all the finally blocks along the way took care of
recovery). This just cleans up the stack trace by removing one layer of
unnecessary wrapping.
Another thing to keep in mind: Scala and other newer JVM languages already
disregard checked exceptions, so you can already find yourself in situations
where a checked exception gets to your top-level handler in Java when
interfacing with other libraries (I've encountered it myself). This just brings
Java closer to parity with other more modern languages.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
