oscerd opened a new issue, #2: URL: https://github.com/apache/camel-kit/issues/2
## Description Integrate the codebase from [luigidemasi/camel-kit-knowledge](https://github.com/luigidemasi/camel-kit-knowledge) directly into the `apache/camel-kit` repository. Currently, `camel-kit-knowledge` is maintained as a standalone repository containing the knowledge layer for `camel-kit` (schema, embedding, indexer, index, and Quarkus MCP server for semantic search across Apache Camel documentation, release notes, CVEs, and component metadata). Consolidating `camel-kit-knowledge` into `camel-kit` will: - Unify the Camel Kit codebase in a single repository - Streamline development, dependencies, and versioning across modules - Simplify CI/CD pipelines, release procedures, and issue tracking under the Apache umbrella ## Expected Behavior - Modules from `camel-kit-knowledge` (e.g., `schema`, `embedding`, `indexer`, `index`, `mcp`) are imported into `apache/camel-kit` as Maven modules (e.g., `camel-kit-knowledge-*` or within a dedicated subfolder/modules in the root `pom.xml`). - Codebase, package names, and Maven group IDs aligned with Apache Camel standards. - Documentation and GitHub Actions workflows consolidated. - Git commit history preserved during the import (e.g. via `git subtree` or `git merge --allow-unrelated-histories`). ## Additional Context - Source repository: https://github.com/luigidemasi/camel-kit-knowledge - Related to Apache migration / groupId alignment (#1) -- 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]
