luigidemasi opened a new pull request, #129: URL: https://github.com/apache/camel-kit/pull/129
Consolidates Kit and the standalone Knowledge MCP server in the Apache Camel Kit repository, while keeping their versions and release schedules independent. Fixes #2. ## Changes - Import the original Knowledge history without rewriting commits, then place the products under sibling `kit/` and `knowledge/` directories. - Add an independently versioned shared Maven parent and aggregator, a main README, product READMEs, and shared Antora documentation under `docs/`. - Move Java packages to `org.apache.camel.kit` and all Knowledge Maven modules to `org.apache.camel`. Knowledge remains usable by MCP clients without Kit. - Keep Kit's published Knowledge 0.0.2 runner pin, with explicit group/version overrides for adopting the new Apache runner. - Separate parent, Kit and Knowledge Maven staging. Index publication is maintainer-triggered and bound to the reviewed commit; clients discover compatible `knowledge-index-v1-*` releases, support exact pins, and retain a usable cached index if an update fails. - Align build workflows, release tooling, source-build instructions and release-versus-development examples with the new layout. Website impact: required and addressed in the shared Antora component and repository documentation. ## Validation - Final head `62814693db58b08ae509ecffc0c46ae51ff0c9b6`: Java 21 full reactor with Linux Ship certification and mandatory vector retrieval (`./mvnw -B -Plinux-ship-certification -Deval.requireVectors=true clean install`) passed: 1,707 tests reported, zero failures/errors, 14 existing optional skips (authenticated Pi live test and optional Knowledge model/network diagnostics). - Final formatting/import gate (`./mvnw -B -Psourcecheck validate`) passed. The full Java 17 reactor also passed before the final documentation-only corrections. - Independent product builds, isolated released-parent resolution, 11 release/distribution tests, and workflow lint passed during migration validation. - Real JBang CLI generation, Camel JBang plugin loading, and packaged MCP discovery/download/search, cached fallback and exact-pin probes passed. - Antora rendered 27 pages with 1,157 local links and one image checked; cross-component references used fixtures. The final README audit checked 53 local links/images and five packaged-runtime/CLI configuration probes. The full reactor includes the 29 documentation consistency tests. - Original Knowledge ancestry and import tree equality verified; all three migration commits are signed. ## History and release transition **Preserve the import merge when landing this PR; do not squash or rebase it.** Original Knowledge head `a5f5a001e3a2ed286598096c7ee0c5b85ea639c6` remains an ancestor. Import commit `8609fd66c4888e9ef1fd4fdc01c768314684a03b` contains a byte-identical copy of its source tree; layout and namespace adaptations are separate commits. The repository currently disables merge commits in the GitHub UI, so landing needs an agreed history-preserving method. Existing released artifacts and download URLs remain valid. New-server default index discovery requires the first compatible index release in `apache/camel-kit`; until then, use the documented local index or explicit legacy manifest URL. Historical tag transfer and release publication are separate maintainer steps. Maven staging does not automatically publish artifacts; the shared release guide retains source-candidate and PMC-vote steps. _AI-generated by OpenAI Codex on behalf of @luigidemasi._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
