The with-java11-non-android-relevant profile was bounded by an upper JDK
version, so with Maven running on JDK 25 the routeconverterjava11extension
fragment was missing from the test runtime. On docker-* branches (tests
on JDK 8 with JavaSE-11.profile) routeconverter then loaded javax.xml.bind
from rt.jar via boot delegation, while Tycho 5's new test TCCL exposes
jaxb-impl's META-INF/services entry, so the bundled impl (wired to the
jaxb-api bundle) got picked, causing JAXB ClassCastExceptions and
IllegalAnnotationsExceptions in com.sap.sailing.server.trackfiles.test.
Assisted-By: Claude Opus 5.5
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Tycho 4.0.x is end-of-life (4.0.13 was the final release); upstream
recommends migrating to the 5.x main line. Tycho 5.x requires Java 21+ as
its runtime VM, which release.yml already satisfies (Maven runs on JDK
25), and still targets the Maven 3.9.x line, so the existing Maven 3.9.11
pin remains valid.
Only java/pom.xml is bumped. The standalone java/com.amazon.aws.aws-java-api
module is deliberately left at Tycho 1.7.0: it builds its local p2 repo
under JDK 8, and Tycho 5.x cannot run on Java 8.
This is an initial probe to see how the release build reacts; serialization/
replication validation (see Bugzilla 3859 note in java/pom.xml) still pending.
Assisted-By: Claude Opus 4.8
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
providerbug6096: first compilable version of sailwave.html result
provider
the persistence test needs to be in the
com.sap.sailing.domain.igtimiadapter.persistence package; but with this
it has to be in a fragment that can legally extend the host bundle's
equally-named package. This was not the case with the
com.sap.sailing.domain.igtimiadapter.test fragment extending the host
bundle com.sap.sailing.domain.igtimiadapter. Moving to a separate
fragment extending the persistence bundle solved that problem.
The problem with WebSocket servlet tests was solved through the hint at
https://github.com/jetty/jetty.project/issues/7835.
moved RiotServer to new bundle to decouple igtimiadapter from
persistence; persistence now knows igtimiadapter, and the server
bundle is expected to fill the RiotServer's state upon activation.
Axel UhlandCopilot