There are a few methods using Throwable.printStackTrace(...). Often System.err might not be visible or the user will not see it, so throwing an exception is more appropriate:
The printStackTrace calls in the static initializer of RuntimeUtils might make sense since you apparently don't want to throw an exception instead (though this would at least fail early; I doubt that any user is checking RuntimeUtils.loaded), but I think the static intializer should probably not call init(); if loading the native lib failed.
There are a few methods using
Throwable.printStackTrace(...). OftenSystem.errmight not be visible or the user will not see it, so throwing an exception is more appropriate:exas causeprintStackTraceon the created exception (instead of throwing and then catching it again). However it might be saner to throw anIllegalArgumentExceptionhere becausenullis not a valid argument there?The
printStackTracecalls in the static initializer ofRuntimeUtilsmight make sense since you apparently don't want to throw an exception instead (though this would at least fail early; I doubt that any user is checkingRuntimeUtils.loaded), but I think the static intializer should probably not callinit();if loading the native lib failed.