RFR: 8268611: jar --validate should check targeted classes in MR-JAR files

[Christian Stein]

On Thu, 12 Dec 2024 15:32:40 GMT, Christian Stein <cstein at openjdk.org> wrote:

>> Maybe this reads better? `release version of {0} too high: {1}`:
>> 
>> release version of META-INF/versions/9/version/Version.class too high: 25
>> release version of META-INF/versions/10/version/Version.class too high: 25
>> 
>> Note that the path of the JAR entry contains the target release version number, and `Version.class` was compiled with `javac` 25 (with `--release 25`).
>
> Prior-art in the messages do read:
> 
> error.release.value.notnumber=\
>         release {0} not valid
> error.release.value.toosmall=\
>         release {0} not valid, must be >= 9
> error.release.unexpected.versioned.entry=\
>         unexpected versioned entry {0} for release {1}

According to above's prior-art, it could just read `release of {0} too high: {1}`

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/22103#discussion_r1882386494