On Wed, Apr 29, 2009 at 12:02 PM, Willem Jiang <willem.ji...@gmail.com> wrote: > Hi riders, > > I'm thinking to do some refactoring of Camel test support to let > camel-core depends on camel-test. > > In this way we just have one copy of TestSupport and CamelTestSupport. > Because camel-test has the dependence of CamelContext , > ProducerTemplate, Service, RouteBuilder, etc, I'd like to break current > camel-core module into camel-api and camel-core, and the camel-test will > depends on the camel-api only. Then we can share the camel-test code > around all the camel-components and camel-core. > > Since CamelTestSupport has the dependency of the CamelBeanPostProcessor > , we could put it into the camel-spring module. > > Any thought? If the only purpose is to keep camel-test in sync with camel-core then I am not keen on this.
We have many interfaces and much more in camel-core that constitutes the API. We have the implementation in component, impl and processor. And working on both in a single project is much easier with SVN and your editor such as Eclipse or IDEA. In the works for Camel 2.0 we have changed or refactored the code numerous times and I doubt it would have been so easy if the code was split. Isnt it possible to keep camel-test in sync by some copy script that can copy the src from camel-core to camel-test so its automatic updated. > > Willem > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
