[jira] [Updated] (POOL-269) Use a generic exception instead of Exception

["Gary D. Gregory (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/POOL-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary D. Gregory updated POOL-269:
---------------------------------
    Summary: Use a generic exception instead of Exception  (was: Specialize useless throws Exception in method signatures)

> Use a generic exception instead of Exception
> --------------------------------------------
>
>                 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
>            Assignee: Gary D. Gregory
>            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)