luigidemasi opened a new issue, #201: URL: https://github.com/apache/camel-kit/issues/201
## Description A pack can work in reactor tests and still lose its descriptor, skill files or service registration when JARs are combined. The Camel CLI plugin also has its own class-loading context. Verify the artifact developers actually install, including how it finds a parser after packaging. Coordinate backend selection with the existing launcher issue. [Kit CLI plugin](https://github.com/apache/camel-kit/blob/79f145c6ebe41dbfdf05a505fca4e357b8ec4caf/kit/camel-jbang-plugin-kit/src/main/java/org/apache/camel/kit/jbang/CamelKitPlugin.java) · [Existing class-loader consideration](https://github.com/apache/camel-kit/blob/79f145c6ebe41dbfdf05a505fca4e357b8ec4caf/kit/camel-kit-core/src/main/java/org/apache/camel/kit/tui/InitTuiView.java#L158-L164) · [JBang and Camel Launcher selection (#110)](https://github.com/apache/camel-kit/issues/110) ## Acceptance criteria - [ ] Assemble the selected pack classes, resources, effective catalog and dependencies into one Kit fat JAR. Preserve required service registrations and plugin entry metadata. Detect duplicate pack resources before publishing the artifact. - [ ] Use a clean Maven fixture to consume the built modules and a fresh workspace to install Kit. Verify skill discovery, invocation through the existing assistant migration workflow and actual parsing of a Mule fixture from inside the packaged artifact. - [ ] Exercise the existing JBang backend and the Camel Launcher backend selected in #110. For Launcher mode, use a supported JDK on a machine without the `jbang` executable and perform a real catalog MCP lookup. Keep backend selection and MCP bootstrap work coordinated with #110 and its documentation follow-up #159. - [ ] Repeat the packaged checks after a module version changes, including a missing or duplicate registration case. Keep pack installation part of the Kit release lifecycle. ## Website impact Required. Update installation and launcher guidance to describe the verified artifact, supported launch paths and diagnostics. _AI-generated by 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]
