In issue #337 we discussed rethrowing the IOException from the API border, but since many methods nowadays don't throws IOException it would be a huge breaking change.
I therefore decided to only change the exception type from RuntimeException to UncheckedIOException to be able to distinguish between them in API consuming business logic. For consumers already catching RuntimeException to handle the wrapped IOException, nothing will change.
In issue #337 we discussed rethrowing the IOException from the API border, but since many methods nowadays don't
throws IOExceptionit would be a huge breaking change.I therefore decided to only change the exception type from RuntimeException to UncheckedIOException to be able to distinguish between them in API consuming business logic. For consumers already catching RuntimeException to handle the wrapped IOException, nothing will change.