Improve smoketester JDK versions support
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
### Description
Currently it is difficult for smoketester to "keep up" with supported java versions, which are moving faster these days.
@uschindler ran into it with the release vote for 9.10, and I ran into it on #12753
From Uwe:
> JAVA_HOME must run be Java 11 (in 9.x)
At moment you can pass "--test-java17 ", but this one is also checked to be really java 17 (by parsing strings from its version output), but I'd like to pass "--test-alternative-java " multiple times and it would just run all those as part of smoking, maxbe the version number can be extracted to be printed out.
So I think the smoketester should require a specific version and check it, for JAVA_HOME. This should be the minimal required java version. But we should also allow passing other JDKs too.
This would make it easier to maintain the logic going forwards.
Contributor guide
Research direction
Start with the smoketester's handling of JAVA_HOME and the existing --test-java17 option. Check how Java versions are parsed and how alternative JDKs are passed, then verify that the minimum JAVA_HOME version is enforced and multiple alternative JDKs can be included; issue 13108 is the linked implementation history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100