camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-263) Move components except bean and mock to a separate maven project
Date Fri, 10 Oct 2008 17:29:52 GMT

     [ 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.


Mime
View raw message