Dave Neuer wrote: > > However, I don't like having no ability to reuse test code from one > project in another project which depends on it. Example: project A has > interface Blah and interface BlahDAO to persist blahs. I have > AbstractBlahDAOTest which has testXXX methods which test *interface > invariant* conditions of BlahDAO. Project B has a new subclass of Blah > and BlahDAO, but it's ProjectBBlahDAO *must* still abide by the > interface invariant constraints. So I want to have ProjectBBlahDAOTest > which extends AbstractBlahDAOTest from project A, but I can't because I > can't generate another (test) artifact in maven. > We experienced similar problems in Cocoon - our workaround is to add another project A-test which contains the all test classes as its source. Then B can depend on A-test with scope "test". But I think this is only a workaround. It would be great if this could be solved somehow in m2 without any tricks.
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
