Hi Jason, > For my projects I put each of those things in a separate project. I > leave unit tests with their component and the other various kinds of > testing in other projects that depend on the component. Don't try and > circumvent the one test source directory. Take the time and partition > your code and you'll be glad you did in the long run.
I want to avoid it to outwit maven. :) How do you handle it with database tests e.g I have a facade for persitence described with interfaces. So would you create seperate the interfaces into a own JAR, then a Mock-Impl-JAR and a Real-Impl JAR? Bye Toby --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
