luigidemasi opened a new issue, #70: URL: https://github.com/apache/camel-kit/issues/70
> Imported from [luigidemasi/camel-kit#126](https://github.com/luigidemasi/camel-kit/issues/126), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-07-03. > Closed by [luigidemasi/camel-kit#127](https://github.com/luigidemasi/camel-kit/pull/127), merged on 2026-07-03. --- ## Description An adversarial final review found a broad defect cluster across graph building/parsing, init/doctor config contracts, generator error handling, distribution/JBang setup, and shipped skill/template guidance. The issues caused silent success on failed graph scans/parses, insecure XML parsing, invalid generated Camel YAML guidance, stale migration facts, missing runtime/version config, and broken distribution/plugin paths. ## Expected Behavior camel-kit should fail loudly on graph/generator/config failures, parse XML securely, persist and validate runtime/version metadata, ship valid distribution/plugin assets, and provide accurate Camel YAML and migration guidance. ## Actual Behavior Several paths swallowed failures or emitted successful output despite broken inputs. Some templates taught invalid Camel YAML or stale component/dataformat mappings. Some distribution and plugin entrypoints referenced unavailable artifacts or omitted required configuration. ## Additional Context Validation: `./mvnw clean install` -- 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]
