You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inspired by #3918 and related discussions, we should consider introducing a mechanism for users to supply arbitrary Java feature versions that are not yet covered by the JRE enum constants.
Note that a "feature" version refers to the leading number in a Java version -- for example, the 21 in 21.0.4. In Java 9, this was referred to as the major number (JEP 223), but the terminology changed to feature in Java 10 (JEP 322).
Deliverables
Investigate options.
The text was updated successfully, but these errors were encountered:
This commit serves as a proof of concept for supporting arbitrary Java
feature numbers in @EnabledOnJre, @EnabledForJreRange, and the JRE enum.
See junit-team#3930
sbrannen
changed the title
Support arbitrary Java feature numbers with JRE conditions
Support arbitrary Java feature versions with JRE conditions
Aug 20, 2024
Overview
Inspired by #3918 and related discussions, we should consider introducing a mechanism for users to supply arbitrary Java feature versions that are not yet covered by the
JRE
enum constants.Note that a "feature" version refers to the leading number in a Java version -- for example, the
21
in21.0.4
. In Java 9, this was referred to as the major number (JEP 223), but the terminology changed to feature in Java 10 (JEP 322).Deliverables
The text was updated successfully, but these errors were encountered: