On Thu, 12 Dec 2024 07:44:50 GMT, Christian Stein <[email protected]> wrote:
>> Please review this change for the `jar` tool to gracefully handle the case
>> where `--release` is not specified as the last arguments.
>>
>> Prior to this commit, operation modes `-d --describe-module` and
>> `--validate` expected to read the optional `--release` option as a file
>> argument: `jar -d -f a.jar --release 9`
>> By adding a hidden GNU-style `--release` option, processing the optional
>> arguments before in those two operation modes, the position is now no longer
>> required to trail behind the `-f --file` option: `jar -d --release 9 -f
>> a.jar`
>>
>>
>> ==============================
>> Test summary
>> ==============================
>> TEST TOTAL PASS FAIL ERROR
>> jtreg:test/jdk/tools/jar 26 26 0 0
>> ==============================
>> TEST SUCCESS
>
> Christian Stein has updated the pull request incrementally with one
> additional commit since the last revision:
>
> Add two more valid use-cases
src/jdk.jartool/share/classes/sun/tools/jar/GNUStyleOptions.java line 347:
> 345: break;
> 346: if (name.equals("--release")) {
> 347: // JDK-8316804: stay here when in `--describe-module`
It's my understanding that we don't include the bug ids in the code comments
within the JDK. The rest of the comment without the bug id I think would be
sufficient.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/22079#discussion_r1890449994
