[
https://issues.apache.org/jira/browse/POOL-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522899#comment-17522899
]
Gary D. Gregory commented on POOL-269:
--------------------------------------
I agree that we can keep binary compatibility since this is all generics and
exceptions in method signatures. Source compatibility is not possible
obviously. I have an experiment in progress.
> Specialize useless throws Exception in method signatures
> --------------------------------------------------------
>
> Key: POOL-269
> URL: https://issues.apache.org/jira/browse/POOL-269
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: Michael Osipov
> Priority: Major
> Fix For: 3.0
>
>
> Too many methods say {{throws Exception}} in their signature. This is neither
> helpful nor good API design. You never know what the exception is and where
> it came from.
> An exception translation pattern has to be applied to make code usable, e.g.,
> like the Spring project does or Maven with {{BuildException}}.
> Unfortunately, this ugly practive has prevailed in several Apache projects
> like Lucene.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
