RE: issue w/ test:test goal being run multiple times when dist goal is executed
Hi, Your message have been already answered in the maven-users list. If the answer don't suit your needs post your thoughts on the thread. This is an issue already discussed by maven developers and I think it will be fixed in next versions. Please don't post this message to maven-dev. This message is appropriate for the maven-users list, as is all non-maven-development traffic. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Springer, Ian P. [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 04, 2004 3:59 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. Is there a workaround for this issue? Any plans to address it in the next release? 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]
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]
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]
RE: issue w/ test:test goal being run multiple times when dist goal is executed
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]
Avoid running multiple goals (was: RE: issue w/ test:test goal being run multiple times when dist goal is executed)
I personally run site with junit, clover and jcoverage reports and would be difficult to skip test:test. I see it more a general question for all plugins. Maven should keep track of goals run and don't run again them. Plugins should be able to override that, e.g. clover could set test:test as not run. I don't know if this was thought for next releases and m2, can anyone tell? I'll move this discussion to developer list. 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 6:41 PM To: Carlos Sanchez; 'Maven Users List' Subject: RE: issue w/ test:test goal being run multiple times when dist goal is executed 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Avoid running multiple goals (was: RE: issue w/ test:test goal being run multiple times when dist goal is executed)
I am also confused as to how goals are determined to be run. I thought it would be like ant where a goal would only be run once. Could someone explain how this is possible and if not why? -Original Message- From: Carlos Sanchez [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 12:03 PM To: 'Maven Users List'; [EMAIL PROTECTED]; 'Maven Developers List' Subject: Avoid running multiple goals (was: RE: issue w/ test:test goal being run multiple times when dist goal is executed) I personally run site with junit, clover and jcoverage reports and would be difficult to skip test:test. I see it more a general question for all plugins. Maven should keep track of goals run and don't run again them. Plugins should be able to override that, e.g. clover could set test:test as not run. I don't know if this was thought for next releases and m2, can anyone tell? I'll move this discussion to developer list. 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 6:41 PM To: Carlos Sanchez; 'Maven Users List' Subject: RE: issue w/ test:test goal being run multiple times when dist goal is executed 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] - 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]
