On Wed, Dec 28, 2011 at 4:18 PM, Glen Mazza <gma...@talend.com> wrote: > Can you just yank it out instead of @deprecate? Test classes are not part > of guaranteed functionality provided to users. >
camel-itest is a test kit for Camel end users. So its public API. http://camel.apache.org/camel-test.html The test kit makes it easier to write unit tests with Camel. That said, we use it of course also a lot in Camel for unit testing the many Camel components we have. > Glen > > > On 12/28/2011 10:08 AM, Claus Ibsen wrote: >> >> Hi >> >> The camel-test component supports currently both JUnit 3.x and 4.x, >> each in separate package. >> Supporting both requires us to have a fair amount of duplicated code, >> one for 3.x and another for 4.x. >> >> I suggest to @deprecated the JUnit 3.x part of the camel-test component. >> Then we can remove support for 3.x in Camel 3.0. >> >> Any thoughts? >> >> > > > -- > Glen Mazza > Talend Community Coders > http://coders.talend.com > blog: http://www.jroller.com/gmazza > -- 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/
