Actually, no. My project has two sub modules. Module A depends on module B and i have it declared as a dependency that module A depends on current module B snapshot.
So, when module A compiles (right after module B) it's going to use the installed snapshot of module B and not it's current source code. Therefore, if i don't install and something changed in module B after its last install, module A won't see the change. So, i have to install everytime. Unless of course, there's another way to configure this use case. Kalle Korhonen wrote: > Ok. Well then, why do you need install? Wouldn't "mvn compile > cobertura:cobertura" be enough? > > Kalle > > > On 1/10/08, *Hugo Palma* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Because i want to run cobertura as part of the CI process that is > pooling for SVN changes. I don't want to generate the site > everytime someone commits to SVN. > Even if i did generate the site, the tests would run twice also, > because i would have to install first. Instead of running "mvn > install cobertura:cobertura" i would run "mvn install site:site" > > > Kalle Korhonen wrote: >> Why don't you just add cobertura as part of the site reports and >> run all of the reports with the site generation? >> >> Kalle >> >> >> On 1/10/08, *Hugo Palma * <[EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>> wrote: >> >> I want run as part of my CI process the goals: >> >> mvn install cobertura:cobertura >> >> The problem is that this causes the test phase to be ran twice. >> Any idea how i can prevent this from happening ? >> >> Thanks. >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> <http://xircles.codehaus.org/manage_email> >> >> >
