ponder-lab / Hybridize-Functions-Refactoring / #3054
85%
main: 85%

LAST BUILD BRANCH: 21586455f64a5fff5574716d9f5751f8916e4be5
DEFAULT BRANCH: main
Ran
Jobs 1
Files 42
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 85.491%. Remained the same
#3054

Pull #944

github

khatchad 
Ignore minor `junit-vintage-engine` bumps the target cannot resolve

The vintage engine enters the target platform through a Maven location
with `includeDependencyDepth="none"`, so only the engine jar arrives and
`org.junit.platform.commons` is supplied by the Eclipse side, where
4.39's JDT test bundles ship the 6.0.x line.

Every 6.1.x engine imports `org.junit.platform.commons.logging [6.1,7)`,
which 4.39 cannot satisfy, so #873 fails at target-platform resolution
rather than in a test. It is not specific to 6.1.3: 6.1.2 carries the
same import, so the whole 6.1.x line is unresolvable until the platform
moves.

Supplying junit-platform 6.1.x ourselves would place a second
`org.junit.platform.commons` beside the JDT test bundles' and pull in
the launcher the engine's `Require-Capability` pins, which is a large
change to the test runtime for an engine whose only job is letting the
`junit6` provider discover JUnit 4 tests (#749). 6.0.3 does that.

Scoped to minor updates so a major bump still opens for review, and
patch updates stay covered by the existing wildcard rule. Lift this when
the target platform ships junit-platform 6.1.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BHbypoDrGUGiBz9xZWt8nd
Pull Request #944: Ignore minor `junit-vintage-engine` bumps the target cannot resolve

3612 of 4225 relevant lines covered (85.49%)

0.85 hits per line

Jobs
ID Job ID Ran Files Coverage
1 #3054.1 42
85.49
Source Files on build #3054