[jira] [Updated] (CAMEL-12598) camel-tooling for code quality checks and anti-patterns

["Claus Ibsen (JIRA)" <ji...@apache.org>]

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

Claus Ibsen updated CAMEL-12598:
--------------------------------
    Fix Version/s: Future

> camel-tooling for code quality checks and anti-patterns
> -------------------------------------------------------
>
>                 Key: CAMEL-12598
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12598
>             Project: Camel
>          Issue Type: New Feature
>          Components: tooling
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: Future
>
>
> We have the camel-maven tooling that can do some scan of your project source code and report mis configured endpoints, and do route coverage reports etc.
> It may be nice to gather a list of anti-patterns and other quality checks for Camel applications that can be commonly used. And then we can see if we can build more tooling to check for this.
> Here is a few on top of my head (not thought for a long time)
>  
> - You could build a check for using deprecated options / components etc. *DONE*
>  
> - Also you can maybe check for too many <when> in a content based router EIP. (like too many if ... elseif ... in java)
>  
> - And maybe also if a route has too many EIPs (eg its too long).
>  
> - Also if a <recipientList> has a single endpoint, then its better to use <toD> which is optimized for a single endpoint. And also has some extra juice for http endpoints.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)