I guess though this comes back to I don't really want to edit my maven.xml or project.xml when i want to turn goals on and off for a specific build.. Although if it is a goal I don't want to ever run, then adding it to the maven.xml would definitly do the trick!
Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 6:46 PM To: Turbine Maven Users List Subject: RE: proposal to remove test:test dependency You can do this by defining the goal in your maven.xml..... -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au [EMAIL PROTECTED] wrote on 03/12/2002 09:38:08 AM: > I do that, but then I forget to switch it back.. > > I do src/test/off as my root, and then switch it back. > > More to the point, I can think of many points where overriding a target > would be useful. For instance, I know that currently when I do maven site, > I fail on the activity target. If I could do: > > maven site -noop=activity test:test then it would run the site target, but > skip the activity and test:test target. > > Eric > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 02, 2002 6:00 PM > To: Turbine Maven Users List > Subject: RE: proposal to remove test:test dependency > > > How about excluding the tests in your project.xml.... > -- > dIon Gillard, Multitask Consulting > Blog: http://www.freeroller.net/page/dion/Weblog > Work: http://www.multitask.com.au > > > [EMAIL PROTECTED] wrote on 03/12/2002 08:59:33 AM: > > > What I would actually like to see is something like a switch passed... > > > > maven war:war /notest to turn off tests. > > > > If you are doing lots of wars quickly, running all the unit tests can > be > > old.. > > > > Eric > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: Monday, December 02, 2002 5:21 PM > > To: Turbine Maven Users List > > Subject: Re: proposal to remove test:test dependency > > > > > > 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]> > > > ForwardSourceID:NT00094ACA > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > ForwardSourceID:NT00094AFE -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
