Distracting "Checksum failed" (ChecksumFailureException) stack trace when installing an extension from the local repository

When one installs an extension from the local maven repository, the following gets logged everytime.

Expected:

• When installing from file://, the checksum could be skipped, or only the message of the exception could be displayed.
• When checksum fails in the regular case when installing from an extension store, the exception should be handled and the message should be logged as warning, without the stack trace. As is, a checksum failure looks like a crash or a bug but it really isn't.

The message is relevant but the full stack trace is distracting and of no use for an admin sys or for a developer working on a JAR extension. It is mostly harmless but these traces take a few seconds to scroll past and burry more useful logs.

Maybe printing the exception could be kept, but using the debug logging level after the warning?