[
https://issues.apache.org/jira/browse/CAMEL-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747001#comment-16747001
]
Claus Ibsen commented on CAMEL-13040:
-------------------------------------
With the splitup of components into individual JARs we have a problem with
spring-boot, as the -starter JARs for camel-core-starter does not include all
these core components. And we cannot do this due to circular-dependencies
between camel-core-starter and camel-direct-starter etc.
It would be a hell for spring boot users to have to add fine grained -starter
for direct, seda, log, etc they may use in their apps.
So we may need to have camel-core-starter include these dependencies somehow.
And it also causes some of the -starter JARs to fail their testing if they use
direct component etc as its no longer on the classpath
> 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
>
>
> 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)
