> So I'm wondering: do I need to actually use the install for modules to "know > about" changes to their dependencies? In other words, could I just do: > > -Navigate to top > -Execute "mvn clean test" > > and module2 would be smart enough to use the target folder of module1 in its > classpath to execute those tests or does module2 always use what has been
Assuming you have the multi-modules set up properly and are executing from the top/shared parent, the reactor should figure out the correct build order for your projects and then use the correct recently-built versions of things as it builds various modules that depend on each other. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
