Yes - install them to the repo on each build, no matter how (CC or manual), but only with "mvn clean install". "install" will run the prior lifecycle steps.
-----Original Message----- From: Mac Systems [mailto:[EMAIL PROTECTED] Sent: Saturday, June 09, 2007 8:15 AM To: Maven Users List Subject: Re: Lifecyle Question Sound Good so far. But i get Confused as i through to know that maven will invoke each of the previous goals. Doing that with Cruise Control mean i have to install each time the snapshots ? the means i have to call somthing like this: "maven clean compile install package site-stage" Is that correct ? thanks, Jens > Sounds like one of your modules has a dependency on a project that > generates > a test-jar. Sorry to say, but you actually have to run "mvn install" - so > the test-jar can be packaged and installed so the module that requires it > can access it. > > It works via "mvn compile" because no test is run, hence no test scope > dependencies. > > Eric > > On 6/7/07, Mac Systems <[EMAIL PROTECTED]> wrote: >> >> Hello Maven Users, >> >> i'd like to how this can happen: >> >> I have an Multiprojekt: >> >> "mvn compile" >> >> work well, all is compiled! >> >> If i do >> >> "mvn package" >> >> i get an Error that some package and test-jar not found. Can someone >> explain a bit how this can happen ? >> >> greets, >> Jens >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
