Use junit5 engine vintage runner to run junit4 tests#15949
Merged
dweiss merged 3 commits intoapache:mainfrom Apr 10, 2026
Merged
Use junit5 engine vintage runner to run junit4 tests#15949dweiss merged 3 commits intoapache:mainfrom
dweiss merged 3 commits intoapache:mainfrom
Conversation
rmuir
approved these changes
Apr 10, 2026
dweiss
added a commit
that referenced
this pull request
Apr 11, 2026
…version catalog is null (it shouldn't be). ##15949
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a dodge-the-problem workaround for gradle/gradle#36508 which switches test execution to junit-platform (vintage runner).
This is also the first step to eventually upgrade to junit jupiter... Not that it's a dramatic change to any existing tests but features of jupiter are quite nice.
I've also started working on moving the randomizedtesting package to jupiter. It isn't a straightforward upgrade (the API is slightly different and some code changes are needed).