you are not understanding lifecycles! "mvn install" means run every stage in the lifecycle upto and including install "mvn deploy" means run every stage in the lifecycle upto and including deploy
"mvn install deploy" means run every stage in the lifecycle upto and including install, then run every stage in the lifecycle upto and including deploy so you are asking it to run twice! Since deploy is after install, you should not need to do "mvn install deploy", just "mvn deploy" -Stephen On Feb 1, 2008 10:45 PM, Cam <[EMAIL PROTECTED]> wrote: > Hi, > > I have a project which launches jetty using the cargo plugin - i have it > starting up as part of the initialize phase and tearing down in compile > (i use it for generating stub classes for a web service). If i run the > install or deploy goals on their own it all works great but if i run > "mvn install deploy" after the install phase it tries to start the > container again even though the phase isn't executed again. This ends up > causing class path problems as it's trying to load the war twice not to > mention the extra hit of having to start and stop the container. > > I would have thought that if you specify a phase which is part of a > later phase they would combine to only execute each once, so since the > install goal is included as part of deploy it would effectively be > ignored. What i find really confusing is how the container can be > started after the install phase when it's bound to 'initialize'. > > Thanks, > Cam > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
