+1 on both counts.
Hadrian
On 12/29/2011 12:54 AM, Willem Jiang wrote:
Here is my +1.
BTW, camel-core unit tests are using the JUnit3 classes because we don't
have the API module to let the camel-test depends on.
I think we can address it in Camel 3.0.
On Thu Dec 29 10:09:29 2011, Daniel Kulp wrote:
+1
I actually forgot about this. A few months ago, I did go through many
of the
in-tree test cases that were still using the Junit3 version and
changed them
to use the Junit4 base class. When I did that, I was going to suggest the
same thing, but forgot. :-(
Dan
On Wednesday, December 28, 2011 4:08:56 PM 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?
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
