[
https://issues.apache.org/jira/browse/CAMEL-23197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luigi De Masi reassigned CAMEL-23197:
-------------------------------------
Assignee: Luigi De Masi
> [camel-jbang-mcp] Extract shared CatalogService with caching and add version
> parameters to all catalog tools
> ------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-23197
> URL: https://issues.apache.org/jira/browse/CAMEL-23197
> Project: Camel
> Issue Type: Improvement
> Reporter: Luigi De Masi
> Assignee: Luigi De Masi
> Priority: Major
>
> Currently, only {{camel_catalog_components}} and
> {{camel_catalog_component_doc}} accept runtime, camelVersion, and platformBom
> parameters to query a version-specific catalog. The remaining 6 catalog tools
> in {{CatalogTools}} and all tools in other classes use new
> {{DefaultCamelCatalog()}} directly, always querying the built-in catalog
> version regardless of the user's project version.
> This means when an AI agent queries camel_catalog_eip_doc for a project
> targeting Camel 4.8.5, it gets options from 4.19.0. Option names, defaults,
> Maven coordinates, and even
> option existence can differ between versions, leading to incorrect code
> generation and false validation results.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
