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 2019/06/07 10:58:00 UTC

[jira] [Assigned] (CAMEL-13620) Camel Main - Move to camel-main ccomponent

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

Claus Ibsen reassigned CAMEL-13620:
-----------------------------------

    Assignee: Claus Ibsen

> Camel Main - Move to camel-main ccomponent
> ------------------------------------------
>
>                 Key: CAMEL-13620
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13620
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0.M4
>
>
> Lets see if we can move the main classes from camel-core to camel-main so they get more separated and become more reusable in other parts.
> We have a common set of options to configure on camel context itself, and all the configuration of components etc. That logic can be more shared for camel main, camel k, camel spring boot, and others etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)