You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/02/05 10:20:00 UTC

[jira] [Assigned] (CAMEL-14461) camel-core - Make RuntimeCatalog optional and in its own module

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

Claus Ibsen reassigned CAMEL-14461:
-----------------------------------

    Assignee: Claus Ibsen

> camel-core - Make RuntimeCatalog optional and in its own module
> ---------------------------------------------------------------
>
>                 Key: CAMEL-14461
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14461
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.1.0
>
>
> Lets see if we can move RuntimeCamelCatalog to its own module and make it optional. 
> Its used by component extension verifiers and components that use dynamic to optimization like toD with http components. But we can look at source code generate what they may need for this, so it can be more optional.
> The new tooling model classes can then also become optional so we can keep plain Camel JARs to less JARs and classes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)