RFR: 8204256: improve jlink error message to report unsupported class file format [v2]
Alan Bateman
alanb at openjdk.java.net
Fri Oct 2 09:37:38 UTC 2020
On Thu, 1 Oct 2020 22:46:43 GMT, Mandy Chung <mchung at openjdk.org> wrote:
>> Ian Graves has refreshed the contents of this pull request, and previous commits have been removed. The incremental
>> views will show differences compared to the previous content of the PR.
>
> Given that linking with JMODs of an unsupported class file version is rare case,
> it's not a bad choice to go with this simplest solution printing the stack trace.
What if we removed the handling of specific exceptions from L278-L285 so that the special handling is limited to
BadArgs? If anything other than BadArgs is throw then it can print the exception to log output along with the cause (if
not null). No objection. That might avoid the tool emitting a "scary" stack trace when an error occurs.
-------------
PR: https://git.openjdk.java.net/jdk/pull/409
More information about the core-libs-dev
mailing list