Align with published QQQ 4.1 and preserve KOF22 integration #24

Merged

james.maes merged 3 commits from feature/kof22-geo-data-canonical into main 2026-11-05 16:16:34 +00:00

Conversation 0 Commits 3 Files Changed 6

+310 -9

james.maes commented 2026-11-05 12:55:56 +00:00

Owner

Copy link

Copy source

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.

james.maes added 1 commit 2026-11-05 12:55:57 +00:00

fix: align the geo data QBit with QQQ 4.1 ... b5787bbe6b

Build against the published QQQ 4.1 core (qqq-bom-pom 4.1.0-RC.21). Mark
City, Country and StateProvince with produceTableMetaData and add the
setters QRecordEntity needs to discover their fields, and make the
producer tolerate a table without fields. Update the producer test.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

james.maes added 1 commit 2026-11-05 13:30:33 +00:00

build: start the 0.2.0 development line ... 6337bfe838

The published 0.1.0 release stays immutable, so the QQQ 4.1 alignment and
the field-discovery fixes move the development revision to the next
unpublished minor, 0.2.0-SNAPSHOT.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

james.maes added 1 commit 2026-11-05 14:44:38 +00:00

build: converge JUnit on 5.10.0 so tests are discovered with the QQQ 4.1 BOM ... 5802fc4adc

CI 4834 (verify 77965) failed with "TestEngine with ID 'junit-jupiter' failed to
discover tests" and ran no test. The published qqq-bom-pom 4.1.0-RC.21 inherits
junit-jupiter-engine and junit-jupiter-params at 6.0.2 from its parent
qqq-parent-project. The project imported that BOM before its own junit-bom 5.10.0,
so the engine and params resolved to 6.0.2 while junit-jupiter, the API and the
platform stayed at 5.10.0; the mixed engine cannot start under Surefire 3.1.2.

Import the pom's existing junit-bom 5.10.0 first (first import wins) so every JUnit
artifact converges on 5.10.0. No version is added or upgraded; the parent and the
QQQ BOM are unchanged. The module and revision relationships are unchanged.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

james.maes merged commit 55edcf4070 into main 2026-11-05 16:16:34 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

bug

Something isn't working

dependencies

documentation

Improvements or additions to documentation

duplicate

This issue or pull request already exists

enhancement

New feature or request

good first issue

Good for newcomers

help wanted

Extra attention is needed

invalid

This doesn't seem right

java

Pull requests that update java code

question

Further information is requested

secuurity

wontfix

This will not be worked on

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

forge-recovery (Forge Recovery) james.maes (James Maes)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-geo-data#24