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 2019/03/01 13:26:00 UTC
[jira] [Updated] (CAMEL-13040) camel3 - camel-core directory layout
[ https://issues.apache.org/jira/browse/CAMEL-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Cosentino updated CAMEL-13040:
-------------------------------------
Fix Version/s: 3.0.0-M1
> camel3 - camel-core directory layout
> ------------------------------------
>
> Key: CAMEL-13040
> URL: https://issues.apache.org/jira/browse/CAMEL-13040
> Project: Camel
> Issue Type: Task
> Components: camel-core
> Affects Versions: 3.0.0
> Reporter: Claus Ibsen
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 3.0.0, 3.0.0-M1
>
>
> I think we should move the splitted camel-core modules into a common parent folder.
> camel-core (POM folder)
> + camel-api
> + camel-core-impl
> + camel-management-api
> + camel-management-impl
> + camel-util
> Then we can have camel-core as a POM for all the sub modules that collectively is "camel-core" as they are in 2.x.
> And we can then continue to splitup the camel-core-impl into smaller pieces, such as the DSL with a camel-dsl-java and camel-dsl-xml
> Just mind that when we do this its harder to backport code fixes from 3.x to 2.x as now the camel-core is not in the same directory location. But this will eventually happen the more camel-core is splitted up into smaller modules.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)