On Thu, 2 Oct 2025 15:45:33 GMT, Marius Hanl <[email protected]> wrote:
> JUnit 6.0.0 is out and we can consider updating to it. > > Release Notes: > https://docs.junit.org/current/release-notes/index.html#release-notes-6.0.0 > > Notes: > - Java 17 is the baseline (so not a problem for us, since we have a higher > baseline) > - Deprecation were removed (not a problem, as we don't rely on any) > - JUnit Vintage Engine is deprecated (not a problem, as we dropped support > for it some months ago) > > JUnit 6 now uses a single version number for all dependencies, that is > platform, jupiter and vintage (which we do not use anymore). That makes > updating it easier. > > It also uses `JSpecify`, which is an annotation library for `@NonNull` and > `@Nullable`. All version numbers for JUnit now use a single variable. @Maran23 This requires a new third-party library, which will need approval. Also, I'll need to review the PR. Since you didn't make any changes to the test source code, I presume that JUnit 6 is compatible with 5 (leaving aside the removed deprecations, which don't affect us), unlike the transition from 4 to 5 (version 5 was effectively an entirely new API). I'll take a look at the release notes, but can you summarize the changes you are aware of? Reviewers: @kevinrushforth @arapte @tiainen or @johanvos ------------- PR Comment: https://git.openjdk.org/jfx/pull/1925#issuecomment-3361994043
