Fix JUnit platform launcher/engine version skew after JUnit 6 upgrade - #237
Merged
Conversation
This updates junit-jupiter to 6.1.3 and explicitly declares junit-platform-launcher at the same version and wires it into both the test and intTest runtime classpaths since Gradle built-in default launcherr only knows about the old JUnit platform 1.x line. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
onobc
force-pushed
the
update-junit-6_1_3
branch
from
August 15, 2026 20:44
22db54d to
cecc612
Compare
lhotari
approved these changes
Aug 15, 2026
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.
junit-jupiter was bumped to 6.1.3, but junit-platform-launcher was left to Gradle's built-in default, which only knows about the old JUnit platform 1.x line. This caused test discovery to fail with "OutputDirectoryCreator not available" since junit-platform-engine 6.x and the injected launcher were unaligned. Explicitly declare junit-platform-launcher at the same version and wire it into both the test and intTest runtime classpaths.