By default it should be fine to use the 'mvn verify' build lifecycle step [1]. In that case the 'reactor' does not reference the project dependencies via the local maven repo but instead via path JVM references to the other modules in the build directly.
LieGrue, strub [1] http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html ----- Original Message ----- > From: Laird Nelson <[email protected]> > To: Maven Users List <[email protected]> > Cc: > Sent: Monday, December 17, 2012 4:34 PM > Subject: Re: Seeking feedback on “Recursive Maven considered harmful” > > On Mon, Dec 17, 2012 at 3:36 AM, Stephen Connolly < > [email protected]> wrote: > >> Another issue is that people abuse the "install" hack far more > often than >> they should... >> > > Hi; this is the first I've read anywhere about the "install > hack". Where > can I find out more about it? > > >> In fact it seems most people's default mode with Maven is to go > "mvn clean >> install". >> > > Guilty as charged in a multi-module build. Are you saying there's another > way that modules in a multi-module build can share artifacts? Could you > point me to where this is documented? > > >> of course the real >> solution is to fix your build so that it works with "clean > verify" on a >> 'virgin' set of version numbers. >> > > To be clear: in a multi-module build, with a root pom, with brand new > version numbers, you're saying the whole build should run just fine when > invoked from the root with "clean verify"? > > Just another user trying to do things right, > Best, > Laird > >> > -- > http://about.me/lairdnelson > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
