+1 Since the beginning of Java, checked exceptions have been the bane of library developers.
I remember using two classes with the same name in Java 1.1. The class which did not have a throws clause was used to compile against. The class with the throws clause was substituted into the final runtime jar. Chas > On Jun 20, 2015, at 2:13 PM, jochenw <[email protected]> wrote: > > Github user jochenw commented on the pull request: > > https://github.com/apache/commons-lang/pull/98#issuecomment-113820743 > > @netomi: "I would prefer to explicitly throw the checked exception wrapped > in a RuntimeException as guava does in its Throwables class." > > That is (IMO) a valid point. OTOH, I'd bet my house on the fact that there > are users out there who will take a different stance. > > In other words: That doesn't mean that we must reject the stuff. If we > document, what problems may, or may not, arise, then let the users decide > whether to use that stuff or not. > > And, besides: Nothing prevents us to add another method, which will use an > UndeclaredThrowableException, or whatever, as a wrapper, and which you and me > will likely prefer. > > > > > --- > 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 [email protected] or file a JIRA ticket > with INFRA. > ---
