-
Notifications
You must be signed in to change notification settings - Fork 422
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
System.exit tests on Java 18 #1503
Labels
theme: build
An issue or change related to the build system
theme: compatibility
Issues related to binary and source backwards compatibility
Milestone
Comments
remkop
added
theme: compatibility
Issues related to binary and source backwards compatibility
theme: build
An issue or change related to the build system
labels
Dec 6, 2021
remkop
added a commit
that referenced
this issue
Dec 6, 2021
remkop
added a commit
that referenced
this issue
Dec 6, 2021
remkop
added a commit
that referenced
this issue
Dec 6, 2021
remkop
added a commit
that referenced
this issue
Dec 6, 2021
remkop
added a commit
that referenced
this issue
Dec 6, 2021
remkop
added a commit
that referenced
this issue
Dec 7, 2021
remkop
added a commit
that referenced
this issue
Dec 7, 2021
remkop
changed the title
Migrate exit-code tests to JUnit 5
System.exit tests on Java 18
Dec 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
theme: build
An issue or change related to the build system
theme: compatibility
Issues related to binary and source backwards compatibility
Many exit-code related picocli tests fail when running on Java 18:
One issue is that migrated tests cannot be run on Java 5, making it harder to verify that the functionality still works as expected on Java 5. So perhaps only the exit-code tests should be migrated.
Note that the issue can be postponed by setting
-Djava.security.manager=allow
before running the tests.The text was updated successfully, but these errors were encountered: