javajavaparser/javaparser #4707Not a task: already works

Upgrading from junit 5.11.4 -> 5.12.1 causes junit exception

envgap__javaparser__javaparser-4707

Original GitHub issue ↗Dated source checkout ↗Opened 2025-04-03

01 / FAILURE SIGNATURE

As reported upstream

Upgrading from junit 5.11.4 -> 5.12.1 causes ‘org.junit.platform.commons.JUnitException: OutputDirectoryProvider not available; probably due to unaligned versions of the junit-platform-engine and junit-platform-launcher jars on the classpath/module path’ errors.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 4b3a4c30a532534796c9d0c9528ba77de641e52d
Manifest: pom.xml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

javaparser/javaparser #4707 · read the original issue

Upgrading from junit 5.11.4 -> 5.12.1 causes ‘org.junit.platform.commons.JUnitException: OutputDirectoryProvider not available; probably due to unaligned versions of the junit-platform-engine and junit-platform-launcher jars on the classpath/module path’ errors.

It is recommended to use the JUnit Platform Bill of Materials (BOM) to align the versions of all JUnit 5 artifacts.

Using the BOM allows you to omit the version when declaring dependencies on all artifacts with the org.junit.platform, org.junit.jupiter, and org.junit.vintage group IDs.

https://junit.org/junit5/docs/current/user-guide/#running-tests-build-maven

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]