This was JUST asked and answered earlier today. from Maarten Volders to Maven Users List date Jun 1, 2007 12:33 AM subject Module B can't find base test class from module A during compilation
As for this being a "shortcoming" of Maven, this is simply an inaccurate statement. Wayne On 6/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I think that this has been dealt with before in the past, but only as a shortcomming of maven. I'm trying to find whether a feature has been added to remedy this... I have two projects that are dependent on each other B --> A. Project A provides some infrastructure that project B uses to implement an application. There exists a project dependency in project B's pom.xml that identifies a dependency on project A and it works for building project B's artifact. In project A's test sources it provides some support objects used for unit testing -- mock objects and the like. Project B's unit tests make use of these objects from Project A's test sources. We are migrating from ant to maven and maven does not make project A's test classes available to project B by default. Is there some way to make classes in project A's *test* sources available to project B's test sources? -- Les Walker --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
