6 Commits

Include renames

Author	SHA1	Message	Date
CI	b6f90e7101	Bump version to 1.2.0-SNAPSHOT [skip ci]	2026-11-07 21:37:18 +00:00
james.maesandClaude Opus 5.5	3fca0c8907	build(deps): align with Gitea releases (parent 2.2.1, QQQ 4.1.0-RC.25) ... base/pom.xml: qqq.version: 4.1.0-RC.22 -> 4.1.0-RC.25 base/pom.xml: qqq.core.version: 4.1.0-RC.22 -> 4.1.0-RC.25 github/pom.xml: qqq.version: 4.1.0-RC.22 -> 4.1.0-RC.25 github/pom.xml: qqq.core.version: 4.1.0-RC.22 -> 4.1.0-RC.25 middleware/pom.xml: qqq.version: 4.1.0-RC.22 -> 4.1.0-RC.25 middleware/pom.xml: qqq.core.version: 4.1.0-RC.22 -> 4.1.0-RC.25 pom.xml: parent -> 2.2.1 pom.xml: revision -> 1.1.0-SNAPSHOT rdbms/pom.xml: qqq.version: 4.1.0-RC.22 -> 4.1.0-RC.25 rdbms/pom.xml: qqq.core.version: 4.1.0-RC.22 -> 4.1.0-RC.25 rdbms/pom.xml: qqq.postgres.version: 4.1.0-RC.22 -> 4.1.0-RC.25 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-07 17:10:19 +00:00
james.maesandClaude Sonnet 5.5	559b738325	fix: keep the literal revision tag out of the root POM comment ... The shared Maven workflow reads the version with grep -m1 on the revision element, so a comment mentioning the element made it parse prose as the version and fail every publish run. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-06 08:20:36 -06:00
james.maesandClaude Sonnet 5.5	034d77b5ac	build: make the reactor root the single version source of every module ... The release pipeline rewrites <revision> only in the ROOT pom.xml (the pinned legacy calculate_version.sh) and nothing passes -Drevision (java-verify runs plain `mvn verify` with MAVEN_ARGS only from caller inputs), but every module declared its own <revision>0.1.0-SNAPSHOT</revision> and did not inherit the root. After an RC rewrite the root would say the RC while the modules still built as the SNAPSHOT, so capture (target/<artifact>-<root version>.jar) would find no JAR and the publisher (one version per reactor) would reject the reactor. Standard Maven CI-friendly inheritance: the root takes the modules' own former parent (qbit-build-parent 2.0.0, identical for all four modules), every module's parent becomes the root (version ${revision}, relativePath ../pom.xml) and the per-module <revision> properties are removed. Each module's inherited build configuration is unchanged (child -> root -> the same qbit-build-parent); modules still build on their own through the relative parent. Metadata audit: the root declares Apache-2.0 and base declares it too (unchanged); rdbms, middleware and github declared no license and inherited qbit-build-parent's AGPL-3.0, so they now state that same license explicitly to keep their published metadata exactly as before (the repository LICENSE is Apache: whether those three should be Apache is an owner decision, not changed here). All GAVs, module boundaries, flatten plugin, dependencies, tests and sources are unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-05 17:23:52 -06:00
James MaesandClaude Sonnet 5.5	2942213e9f	build: flatten the reactor root POM so the publisher can accept it ... The reactor root (qbit-scripting-reactor, pom packaging, version ${revision}) is itself a module the qrun publisher captures and enrolls; without the flatten plugin its consumer POM keeps the unresolved ${revision} and the publisher rejects it. No source or dependency change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-05 17:23:52 -06:00
3 people	f0d695ec97	chore: preserve paused QBit work and document remaining issues ... Save the current implementation and README, status, and known-issue documentation at the user-requested stop. No completed release or deployment is claimed. Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: GPT-6 Codex <noreply@openai.com>	2026-11-04 10:45:28 -06:00