You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2007/12/15 19:20:27 UTC
[jira] Created: (CAMEL-263) Move components except bean and mock to
a separate maven project
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.3.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.
[jira] Commented: (CAMEL-263) Move components except bean and mock
to a separate maven project
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46350#action_46350 ]
Claus Ibsen commented on CAMEL-263:
-----------------------------------
We will get complications with the build order in maven, as we use the current components extensively in unit testing camel-core itself.
> 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: 2.0.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.
[jira] Commented: (CAMEL-263) Move components except bean and mock
to a separate maven project
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42246#action_42246 ]
Christian Schneider commented on CAMEL-263:
-------------------------------------------
I don´t mean each component should be in it´s own package. But a package with the basic components could be easily separated from the core. The separation would make sure that no core class references a component class.
> 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.
[jira] Commented: (CAMEL-263) Move components except bean and mock
to a separate maven project
Posted by "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.
[jira] Resolved: (CAMEL-263) Move components except bean and mock
to a separate maven project
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-263.
-------------------------------
Resolution: Won't Fix
> 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: 2.0.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.