Hi,
The main issue was the upgrade of junit5. The current version is bullseye:
junit5/oldstable,now 5.3.2-4 all [installed,automatic]
has a mispackaged
-rw-r--r-- 1 root root 7489 Nov 22 2020
/usr/share/java/junit-platform-console-standalone-1.3.2.jar
Fixing this leads to the next issue - jtreg7 uses 5.9.1 API:
./src/share/classes/com/sun/javatest/regtest/agent/JUnitRunner.java:34:
error: cannot find symbol
import org.junit.platform.launcher.LauncherSession;
^
symbol: class LauncherSession
location: package org.junit.platform.launcher
../src/share/classes/com/sun/javatest/regtest/agent/JUnitRunner.java:141:
error: cannot find symbol
try (LauncherSession session =
LauncherFactory.openSession(launcherConfig)) {
^
symbol: class LauncherSession
location: class JUnitRunner
../src/share/classes/com/sun/javatest/regtest/agent/JUnitRunner.java:141:
error: cannot find symbol
try (LauncherSession session =
LauncherFactory.openSession(launcherConfig)) {
^
symbol: method openSession(LauncherConfig)
location: class LauncherFactory
3 errors
This was the point where I've started considering vendoring it, as
doing a minor version upgrade will introduce new dependencies
(opentest4j-reporting) and a number of breaking changes that will
require rebuilding reverse dependencies and fixing any issues found.
Best Regards,
Vladimir.
On Thu, May 2, 2024 at 8:39 PM Emmanuel Bourg <[email protected]> wrote:
>
> Hi Vladimir
>
> On Mon, 08 Apr 2024 20:38:45 +1200 Vladimir Petko <[email protected]> wrote:
>
> > jtreg7 depends on newer versions of the Java packages such as junit4,
> > junit5,
> > hamcrest, etc. Updating them in the stable releases will require significant
> > effort.
>
> jtreg7 is already in bookworm. Did you mean bullseye?
>
> What errors do you get when building with the available dependencies?
> That might be easily fixable.
>
> Emmanuel Bourg
