log classfile format exceptions more aggressively (Bugzilla Bug 461125)

[mcculls]

This issue was created automatically with bugzilla2github

Bugzilla Bug 461125

Date: 2015-02-28 07:54:15 -0500
From: Igor Fedorenko <[email protected]>
To: Project Inbox <[email protected]>

Last updated: 2015-02-28 07:54:15 -0500

Comment 2525175

Date: 2015-02-28 07:54:15 -0500
From: Igor Fedorenko <[email protected]>

We provide a set of Maven core extensions that are built for java 7. These components are deployed into Maven installation lib/ext directory and are expected to be automatically discovered and used. We had number of rather difficult to troubleshoot bug reports from users who accidentally used java 6 to run Maven. There was no error message or anything else to indicate incompatible java version as the root cause of the problem, so from the user point of view our Maven extensions simply did not work.

I think Sisu should at least log incompatible classfile versions as error so they become more easily visible to the user. Ideally, though, I think Sisu should raise an exception when incompatible classfile is encountered during component discovery.