Build against published qqq-bom-pom 4.1.0-RC.21 and incorporate the reviewed compatibility changes used by KOF22. This moves the integration into the owning library so KOF22 can consume its published JAR/POM. Existing CI is unchanged. Validation: source review completed; native checks run on this PR. No local full-suite rerun.
Build against published qqq-bom-pom 4.1.0-RC.21 and incorporate the reviewed compatibility changes used by KOF22. This moves the integration into the owning library so KOF22 can consume its published JAR/POM. Existing CI is unchanged. Validation: source review completed; native checks run on this PR. No local full-suite rerun.
Import qqq-bom-pom 4.1.0-RC.21 unconditionally ahead of the parent's BOM
and port the test base to the 4.1 API: QInstance.setAuthentication no
longer exists, so BaseTest uses withInstanceDefaultAuthentication. The
development revision and the parent are unchanged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
CI 4712 verify 74837 ran 0 tests: "TestEngine with ID 'junit-jupiter' failed to discover tests". The cause (reproduced with
the CI Maven 3.9.11 image and read from the surefire dump) is a mixed JUnit stack: qbit-build-parent 1.4.0 manages
junit-jupiter and the platform at 5.10.0, while the imported qqq-bom-pom 4.1.0-RC.21 manages junit-jupiter-engine and
-params at 6.0.2, so Jupiter engine 6.0.2 runs on platform-engine 1.10.0 and fails with NoClassDefFoundError
org.junit.platform.engine.support.discovery.DiscoveryIssueReporter. Import the parent's own junit-bom 5.10.0 before the QQQ
BOM (first import wins) so every JUnit artifact is 5.10.0. No version is upgraded or downgraded beyond that convergence;
no test, assertion, production code, JaCoCo or surefire setting changes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Build against published qqq-bom-pom 4.1.0-RC.21 and incorporate the reviewed compatibility changes used by KOF22. This moves the integration into the owning library so KOF22 can consume its published JAR/POM. Existing CI is unchanged. Validation: source review completed; native checks run on this PR. No local full-suite rerun.