I think it is bad style to catch (checked) Exceptions and wrap them into
Runtime just for "not having to catch them". If the API forbidds throwing
cached exceptions there is of course o other way, but even there there a
global "catch all exceptions" should be decided with care, it is almost
Is there no @SuppressWarning to Mark the exceptions (pun intended)?
On Aug 23, 2017 11:36, "Christian Schneider"
wrote:
> Currently the checkstyle rules forbid to catch Exception.
>
> I propose to change this as catching Exception is sometimes very useful
> when for
Currently the checkstyle rules forbid to catch Exception.
I propose to change this as catching Exception is sometimes very useful
when for example a called method throws Exception or we simply want to
map to RuntimeException to avoid having throws Exception in every caller.
Christian
--