Currently if a jlink plugin throws an exception, only getMessage() is printed.

Consider allowing users to enable more detailed output as a debugging aid, primarily dumping the stacktrace. Information about which plugin threw the exception together with the input to jlink and to the specific plugin (useful when you're note the one explicitly running jlink, say, via the JDK build) could also be helpful.