Thanks for your contribution, @benjamin-bader. It looks good to me. @komamitsu, could you check this issue?

@benjamin-bader I noticed that the original e.printStackTrace() is outputted regardless of the log level. But in your change, the stack trace is hidden if the log level is more than FINE.

Also, we can output the stack trace of a Throwable using java.util.logging.Logger#log(java.util.logging.Level, java.lang.String, java.lang.Throwable). So maybe we don't need to create org.msgpack.util.Exceptions.

Originally, that error message is important and I think we should've outputted it as a higher log level with its stack trace...

After all, something like the following code seems better to me. What do you think?

    } catch (SecurityException e) {
        LOG.log(Level.WARNING, "Cannot append a search path of classloader", e);

@komamitsu Sounds good, thank you for the feedback. I'll fix and update today.

@benjamin-bader Sorry for my delay and thanks for your contribution!

Thank you @komamitsu! I had assumed this section of the codebase was obsolete in the upcoming 0.7 release - glad to hear that this may still be useful.