On 17 December 2012 15:34, Laird Nelson <[email protected]> wrote: > 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"? >
I am not saying that you only ever run it with "clean verify" I am not saying running with "clean install" is considered harmful. I am saying that *if* you _need_ to use "clean install" then your build is not the best it could be and you may have issues with your build that you haven't noticed. If you have a big multi-module build and are only working in one small part, by all means do $ git pull $ mvn clean install $ mvn clean install -pl foo:bar -am (or -amd depending on your needs) $ mvn clean install -pl foo:bar -am ... $ mvn clean install -pl foo:bar -am Just don't assume that you always have to run as far as install... and make sure your build doesn't require it also > > Just another user trying to do things right, > Best, > Laird > > > > -- > http://about.me/lairdnelson >
