[ 
https://issues.apache.org/jira/browse/CAMEL-27070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-27070.
---------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/camel/pull/30219 (commit 3b72f5ac on main), 
released in 4.24.0.

_Claude Code on behalf of davsclaus_

> camel-jbang - list the Kamelets from the index in the camel-kamelets JAR
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-27070
>                 URL: https://issues.apache.org/jira/browse/CAMEL-27070
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> camel catalog kamelet takes about 720 ms. Most of it goes into loading the 
> whole Kamelets catalog to list four fields per Kamelet: the Maven resolve of 
> camel-kamelets-catalog (~170 ms), KameletsCatalog and Jackson start (~110 
> ms), the classpath scan (~230 ms) and binding the 259 Kamelet YAMLs to the 
> CRD model (~210 ms).
> camel-kamelets now ships an index of its Kamelets in the camel-kamelets JAR, 
> META-INF/kamelets-index.json (apache/camel-kamelets#3137, part of 
> apache/camel-kamelets#3133): name, type, support level, title, description, 
> group, namespace and provider of each Kamelet. The Camel CLI has the 
> camel-kamelets JAR of its default Kamelets version on its class path.
> When the Kamelets version asked for is the one of that JAR, the commands that 
> only list Kamelets read the index instead of the catalog: camel catalog 
> kamelet, the names for export and for "did you mean" in camel catalog doc, 
> and the MCP kamelet list tool. For another version, or a camel-kamelets JAR 
> without the index (4.23.0 and older), they load the catalog as before.
> The index is in camel-kamelets from 4.24.0, so the gain shows once Camel uses 
> that release.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to