Don't add "-o" to this. That's something different not impacting artifacts produced in a multi-module build.
"install" is not required for a multi-module build. (It is sometimes when using Maven 2, but everyone should be using Maven 3 so this is not a problem.) The so-called reactor of a multi-module build will handle the artifact not being present but rather use the content of the target folders. /Anders On Tue, May 8, 2012 at 6:09 PM, Laird Nelson <ljnel...@gmail.com> wrote: > On Tue, May 8, 2012 at 12:05 PM, Anders Hammar <and...@hammar.net> wrote: > >> Doing "mvn dpeloy" on a larger multi-module build will not do this for >> the latter part of the build. So, what you want is "mvn test". > > > Dumb, slightly tangential question: will mvn -o clean test on a > multi-module build work? My assumption (untested, to be sure) is that it > would not. I would think that "install" is still necessary for tests in a > given module that depend on artifacts produced by another module, so that > those artifacts are present in the local repo. > > Best, > Laird > > -- > http://about.me/lairdnelson --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
