Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support arbitrary Java feature versions with JRE conditions #3930

Open
1 task
sbrannen opened this issue Aug 20, 2024 · 1 comment
Open
1 task

Support arbitrary Java feature versions with JRE conditions #3930

sbrannen opened this issue Aug 20, 2024 · 1 comment

Comments

@sbrannen
Copy link
Member

sbrannen commented 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 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.
@sbrannen sbrannen added this to the 5.12 M1 milestone Aug 20, 2024
@sbrannen sbrannen self-assigned this Aug 20, 2024
sbrannen added a commit to sbrannen/junit5 that referenced this issue Aug 20, 2024
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
Copy link
Member Author

@sbrannen sbrannen changed the title Support arbitrary Java feature numbers with JRE conditions Support arbitrary Java feature versions with JRE conditions Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant