Edelson, Justin wrote: > > It sounds like you want a test-jar. See > http://maven.apache.org/guides/mini/guide-attached-tests.html >
Aha :) That builds the tests into myproject-tests.jar indeed... > I don't know how you could do this in Eclipse other then have the > Eclipse project have the test-jar in it's build path. I don't think > Eclipse can support a separate classpath for tests from main code. You > can specify additional classpaths when you run each test, but that's a > lot of effort and still wouldn't let you compile the test classes. > Right; so the Maven 2 Dependencies build path library doens't get the the -tests.jar. I'm sure I could reference th external jar directly (or even the test-classes path for the sibling project), but then it'd go away when I did an mvn clean. There's no way the m2 plugin for Eclipse can include things with <type>test-jar</type> in the build path? I think that'd do it... I don't care so much if this superfluous-at-deploy-time jar is in the Eclipse build path, since mvn install/deploy/whatever would do the right thing in the end. 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#a4665985 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
