My take on this is it's the same rationale as a jar. If the tests don't pass, don't build the deliverable. -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au
"Matt Ho" <[EMAIL PROTECTED]> wrote on 03/12/2002 06:41:19 AM: > Can I suggest that we remove the > > <attainGoal name="test:test"/> > > task for the war:war target? It seems inappropriate to force all the > unit tests to be run just to build the war file. It seems to me that > users are always able to call > > maven test:test > > explicitly. Having war:war call test:test means that: > > * if you have a lot of unit tests, this can be an extremely long > > operation. This can be especially painful if all you want to > do > is rebuild the war file after making a minor modification > > * if the machine you intend to perform builds on is not > configured > to run the tests, you can't build the war file > > Any comments would be appreciated :) > > -- > Matt Ho > Principal > Indigo Egg, Inc. > http://www.indigoegg.com/ > > > > -- > To unsubscribe, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > > ForwardSourceID:NT00094A1A -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
