Yeah, I'm actually thinking that the pregoal would be the way to go.. But, I see it as something you configure your project.. for example, if you want the tests to run, but you need to do the bytecode manipulation, then set the preGoal to set maven.test.skip=true after running once, and have clover or jcoverage run first..
If you run either first, and then run the junit report, it doesn't have to run the test:test again... What clover or jcoverage output has everything the report needs.. Eric > -----Original Message----- > From: Carlos Sanchez [mailto:[EMAIL PROTECTED] > Sent: Friday, July 30, 2004 5:44 PM > To: 'Maven Users List'; [EMAIL PROTECTED] > Subject: RE: issue w/ test:test goal being run multiple times when dist > goal is executed > > > Hi, > > Just be sure that it does't break plugins that need to rerun test:test as > clover or jcoverage. > > Regards > > Carlos Sanchez > A Coru�a, Spain > > Oness Project > http://oness.sourceforge.net > > > -----Original Message----- > > From: Eric Pugh [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 30, 2004 5:41 PM > > To: Maven Users List > > Subject: RE: issue w/ test:test goal being run multiple times > > when dist goal is executed > > > > I've seen the same thing, and actually thought about some > > fixes.. Could > > make junit-report smarter to only run if the unit test report > > files don't exist. Could also introduce some sort of pregoal > > to test:test that checks and if the tests have been run, then > > set maven.test.skip=true.. > > > > Eric > > > > > -----Original Message----- > > > From: Springer, Ian P. [mailto:[EMAIL PROTECTED] > > > Sent: Monday, July 26, 2004 6:48 PM > > > To: [EMAIL PROTECTED] > > > Subject: issue w/ test:test goal being run multiple times when dist > > > goal is executed > > > > > > > > > When I run "maven dist", my project's unit tests get run > > three times: > > > > > > 1) because test:test is a prereq of jar:jar > > > 2) because test:test is a prereq of war:webapp > > > (which I call from a dist:prepare-bin-filesystem postgoal in > > > maven.xml) > > > 3) because junit-report:report does an attainGoal of test:test > > > > > > Running the unit test three times slows down the dist build > > and also > > > clutters Maven's output. Does anyone know of a workaround for this > > > issue? > > > > > > Thanks, > > > Ian > > > > > > > > --------------------------------------------------------------------- > > > 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]
