[jira] Commented: (CAMEL-263) Move components except bean and mock to a separate maven project

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

    [ https://issues.apache.org/activemq/browse/CAMEL-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42243#action_42243 ] 

Claus Ibsen commented on CAMEL-263:
-----------------------------------

-1

Then all the people need a lot of more dependent jars to work with Camel.

I would even argue that some of the camel-spring components should be in the core or camel-core and came-spring be merged.
When you combine Camel and Spring gives you the outstanding power.



> Move components except bean and mock to a separate maven project
> ----------------------------------------------------------------
>
>                 Key: CAMEL-263
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-263
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Christian Schneider
>             Fix For: 1.4.0
>
>
> Most of the components (except bean and mock) below package components are not referenced from the rest of the camel code. So my suggestion is to move these into a separate maven project that could be called camel-components-standard. The new project will of course include camel_core but camel_core will not need to include the components. 
> The only components that are heavily referenced from the rest of the camel_core are bean and mock. These will have to stay in the maven core project of course.
> The separation will make understanding the camel core code easier as it gets smaller.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.