Bump com.ginsberg:junit5-system-exit from 1.1.2 to 2.0.2

[dependabot]

Bumps com.ginsberg:junit5-system-exit from 1.1.2 to 2.0.2.

Release notes

Sourced from com.ginsberg:junit5-system-exit's releases.

Release v2.0.2

This is a bugfix release and is a drop-in replacement for version 2.0.0 and 2.0.1.

ChangeLog

• Fix #24 - Reset test between assertion calls

Release 2.0.1

This is a bugfix release and is a drop-in replacement for version 2.0.0.

ChangeLog

• Fix #20 - Multiple calls to System.exit() do not always register the first exit code as the cause.

Release 2.0.0 - New Java Agent-based Approach

Version 2.0.0 removes the terminally deprecated SecurityManager approach and now uses a Java Agent to rewrite bytecode as the JVM loads classes. Whenever a call to System.exit() is detected, the JUnit 5 System Exit Agent replaces that call with a function that records an attempt to exit, preventing the JVM from exiting. As a consequence of rewriting bytecode, this library now has one dependency - ASM.

Please see the Project README for comprehensive install instructions.

ChangeLog

• Remove terminally deprecated SecurityManager approach for preventing System.exit() calls
• Add Java Agent-based approach. Calls to System.exit() are rewritten as classes are loaded
• Add AssertJ-style fluid assertions for cases when test authors do not want to use annotations, or want to write assertions after a System.exit() is detected
• Upgrade Gradle to 8.10
• Upgrade JUnit to 5.11.0
• Switch to Kotlin DSL from Groovy DSL in Gradle build
• Switch to GitHub Actions for build runner

Changelog

Sourced from com.ginsberg:junit5-system-exit's changelog.

2.0.2

• Bugfix: [#24](tginsberg/junit5-system-exit#24): Reset state between assertion calls.

2.0.1

• Bugfix: [#20](tginsberg/junit5-system-exit#20): Multiple calls to System.exit() do not always report the first exit status code.

2.0.0

• Remove terminally deprecated SecurityManager approach for preventing System.exit() calls.
• Add Java Agent-based approach. Calls to System.exit() are rewritten as classes are loaded.
• Add AssertJ-style fluid assertions for cases when test authors do not want to use annotations, or want to write assertions after a System.exit() is detected.

Commits

• 44dd8af Release v2.0.2
• 5bc161f Fix #24 - Reset state between assertion calls (#25)
• b62a041 Prepare v2.0.2
• 3981ad6 Release v2.0.1 (#23)
• 578b6b5 Feature/18 maven documentation fix (#19)
• 89102e8 Rev to 2.1.0-SNAPSHOT (#17)
• b782d38 v2.0.0 - Java Agent-based approach (#16)
• 258efc9 Update README.md
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)