Currently JDKSelector#fillJavaSEVersion adds a candidate SE version to a supported server's drop list for a given MP version if either the minimum MP version qualifies or the maximum MP version qualifies.
The logic should require both conditions to be true.
You can see this by temporarily adding an entry for SE17 to JavaSEVersion and then changing JDKSelector so a server has three combinations of supported SE version (see diffs below). IIUC the revised JDKSelector should require SE 11 for Helidon supporting MP 3.2 and 3.3 and should require SE 17 for Helidon supporting MP 5.0. But if you build and run the starter with these changes, the SE drop list for Helidon/MP 5.0 incorrectly contains both 11 and 17.
Currently
JDKSelector#fillJavaSEVersion
adds a candidate SE version to a supported server's drop list for a given MP version if either the minimum MP version qualifies or the maximum MP version qualifies.The logic should require both conditions to be true.
You can see this by temporarily adding an entry for
SE17
toJavaSEVersion
and then changingJDKSelector
so a server has three combinations of supported SE version (see diffs below). IIUC the revisedJDKSelector
should require SE 11 for Helidon supporting MP 3.2 and 3.3 and should require SE 17 for Helidon supporting MP 5.0. But if you build and run the starter with these changes, the SE drop list for Helidon/MP 5.0 incorrectly contains both 11 and 17.