Hi I guess if we have hamcrest by default in camel-test and we have nice reading assertions using it then it would be much easier for end users (and our self) to write unit tests. It's pretty cool, but not used much as you need to learn and understand how to use it. But if it's there from day-1 then I will be more inclined to start using it. Espeically if the code is easier to read and understand but also I can do more in fewer lines of code.
And log4j is my logger of choice so I don't mind it be there as well. But if it had scope=test I guess I will get my logging output as I want it /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/ On Mon, Dec 1, 2008 at 9:23 PM, James Strachan <[EMAIL PROTECTED]> wrote: > 2008/12/1 Claus Ibsen <[EMAIL PROTECTED]>: >> Hi >> >> Much better. >> >> Is hamcrest needed as a dep? its in the pom.xml? > > Its not needed yet - I was gonna hopefully add a load of nice hamcrest > assertion methods; but those can go in the camel-hamcrest module. > >> And log4j. as well. It could be optional, for those few end users that >> use java util logging. > > Yeah agreed. I added it really to minimise the amount of stuff you've > gotta remember to add to the pom.xml to get decent output out :) But I > guess we can zap it - or specify it as test scope (so only used in its > own test cases). > > I was thinking we should consider porting the camel-core test cases in > org.apache.camel.processor to this module and making them exemplars of > good tests folks can copy > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ >
