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 always better to catch indivual types and rethrow with a sensible hint whats going wrong.
Beside that you can always disable checkstyle rules for a given code path. Am Mittwoch, 23. August 2017 11:36:34 UTC+2 schrieb Christian Schneider: > > 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 > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > > -- -- ------------------ OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
