[
https://issues.apache.org/jira/browse/CAMEL-25403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-25403:
--------------------------------
Fix Version/s: 4.23.0
(was: 4.24.0)
> camel-jbang - AI tools: note a Kamelet camel: dependency that the template
> does not use
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-25403
> URL: https://issues.apache.org/jira/browse/CAMEL-25403
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.23.0
>
>
> The Kamelet file checks of the AI tools (KameletChecks, CAMEL-25379) report a
> spec.dependencies entry whose camel:<name> is not a Camel component, but not
> one that names a real component the template does not use.
> In the local model benchmark (qwen3.6:35b-a3b through the camel-jbang-mcp
> server, Kamelet side check, Oct 7 2026), the model wrote a custom action
> Kamelet whose template is only a setBody with a simple expression, and listed:
> {code}
> dependencies:
> - "camel:timer"
> {code}
> in 3 of 5 runs. It is harmless (timer is in camel-core), but wrong: it is
> likely copied from the source Kamelet sample in kamelet-custom.adoc, which
> declares camel:timer because its template starts from a timer, or from the
> timer of the route that uses the Kamelet. A dependency that brings in a real
> library would add it to an exported project for nothing.
> Proposal: when a camel:<name> dependency names a component, data format or
> language that the template does not use (no uri with that scheme, no data
> format or language of that name), add a note, not an error, e.g.
> "spec.dependencies: camel:timer is not used by the template: list only the
> components, data formats and languages the template uses". Optionally the
> kamelet-custom.adoc samples could say the same next to their dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
