Right, sorry for the flurry of questions... We have a parent project P and two projects A and B inside it. A/src/test/java/foo/bar has a class DatabaseTestCase. Now I need to write a database test in B, so I'd like to import foo.bar.DatabaseTestCase.
However, although B has a dependency on A, it doesn't get the test class files in the JAR, so the import fails. I could always move the common base classes to the main package, but then I get dependencies on JUnit and DBUnit, which are obviously still only necessary when running tests (be they for A or B). Can Maven handle this? Can Eclipse handle this? :) Martin -- View this message in context: http://www.nabble.com/Letting+the+tests+of+one+project+depend+on+the+tests+of+another+one-t1717855.html#a4665455 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
