You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2026/03/10 09:55:00 UTC

[jira] [Assigned] (CAMEL-23165) camel-jbang - MCP tool that analyze a camel component for known bugs

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

Andrea Cosentino reassigned CAMEL-23165:
----------------------------------------

    Assignee: Andrea Cosentino

> camel-jbang - MCP tool that analyze a camel component for known bugs
> --------------------------------------------------------------------
>
>                 Key: CAMEL-23165
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23165
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 4.x
>
>
> A MCP tool that checks Jira / commit log for a given camel component, and analyze how many open bugs, fixed bugs, and commits a component has over time. To help analyze its quality. This can also analyze the time for bug report to fix how long that takes.
> It can also help tell which components are slowing down (it may also be that they are just great quality). But in general some component has not changed in years.
> The analysis of git would then likely need to understand that there are some commits that just bump versions, pom.xml and not actual important code change, so look for java changes in src/main/java. 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)