Partest tests can require a java version range

[lrytz]

... using a // javaVersion: N / N+ / N - M comment in the test soruce.
The test is skipped if the java version is outside the range.

[som-snytt]

Ha, already looked at this when I woke up. Wondering if it means we can get rid of the "pragma" on the check file: control the version on the input side, not the output.

[lrytz]

I didn't add support for java version ranges to keep it simple, but that would also be a possibility. Getting rid of the pragmas in check files would then mean duplicating the test, which doesn't gain us much I think...

[som-snytt]

--update-check doesn't respect pragmas in check files, and probably never will.

There are only a few tests that are version or platform dependent. Maybe instead of range, just jdk: 11 17 where someone testing locally with 16 will see a skipped test, which is reasonable.

[lrytz]

I agree that maintaining .check files with pragmas is a huge pain. Though switching jvm for a "quick" --update-check will be not so quick either :-)

I can do version ranges.

[som-snytt]

toolArgsForTheWin

[lrytz]

Changed to support java version ranges, also added some doc to CONTRIBUTING.md

[harpocrates]

Thank you so much for adding this, and so promptly too. ❤️