You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by Vincent Massol <vm...@pivolis.com> on 2003/11/17 17:02:06 UTC

[Plugin test] Why call clean after the test?

Hi dIon,

I'm starting to move my sample plugin apps into plugin tests (using
src/plugin-test and the "testPlugin" goal). I've noticed you have
followed the following pattern:

  <goal name="testPlugin" prereqs="test-changes-report">
    <attainGoal name="clean"/>
  </goal>

I'm wondering why you call clean after the test is done? Why not:

  <goal name="testPlugin" prereqs="clean,test-changes-report"/>

instead?

Anything I'm missing?

Thanks
-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [Plugin test] Why call clean after the test?

Posted by di...@multitask.com.au.

"Vincent Massol" <vm...@pivolis.com> wrote on 18/11/2003 03:02:06 AM:

> Hi dIon,
> 
> I'm starting to move my sample plugin apps into plugin tests (using
> src/plugin-test and the "testPlugin" goal). I've noticed you have
> followed the following pattern:
> 
>   <goal name="testPlugin" prereqs="test-changes-report">
>     <attainGoal name="clean"/>
>   </goal>
> 
> I'm wondering why you call clean after the test is done? Why not:
> 
>   <goal name="testPlugin" prereqs="clean,test-changes-report"/>
> 
> instead?
> 
> Anything I'm missing?

Reasons:
1) I didn't want to have to sprinkle .cvsignore files everywhere.
2) Clean would sometimes fail as a pre-req due to weird reactor 
interactions.

If it works for you, leave clean as a postreq.
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org