Hi In the recent work by GNodet to add a new camel-test-blueprint, which I have recently polished. I noticed that the camel-test classes for CamelTestSupport has dependency on Spring JARs. This is not the intent, as there is a CamelSpringTestSupport people should use if they use Spring.
So I wonder if it would make sense for us to split camel-test into - camel-test - camel-test-spring eg to move the Spring Test support to a new component. Then we have a vanilla camel-test component that has just dependency on JUnit. This may aid end users, who are not using Spring, that we drag in Spring JARs when they use camel-test. Any thoughts? -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
