Return-Path: Mailing-List: contact turbine-maven-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list turbine-maven-user@jakarta.apache.org Received: (qmail 23185 invoked by uid 98); 3 Dec 2002 03:38:20 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 23144 invoked from network); 3 Dec 2002 03:38:18 -0000 Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 3 Dec 2002 03:38:18 -0000 Received: (qmail 43342 invoked by uid 500); 3 Dec 2002 03:37:04 -0000 Received: (qmail 43335 invoked from network); 3 Dec 2002 03:37:03 -0000 Received: from unknown (HELO beholder.brekke.org) (24.211.22.7) by daedalus.apache.org with SMTP; 3 Dec 2002 03:37:03 -0000 Received: from beholder.brekke.org (localhost.localdomain [127.0.0.1]) by beholder.brekke.org (8.12.5/8.12.5) with ESMTP id gB33amv4019310 for ; Mon, 2 Dec 2002 21:36:49 -0600 Received: from localhost (jbrekke@localhost) by beholder.brekke.org (8.12.5/8.12.5/Submit) with ESMTP id gB33alkR019306 for ; Mon, 2 Dec 2002 21:36:48 -0600 X-Authentication-Warning: beholder.brekke.org: jbrekke owned process doing -bs Date: Mon, 2 Dec 2002 21:36:46 -0600 (CST) From: "Jeffrey D. Brekke" X-X-Sender: jbrekke@beholder.brekke.org To: Turbine Maven Users List Subject: Re: proposal to remove test:test dependency In-Reply-To: <011201c29a3a$c98f2f20$1001a8c0@coily> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N One of the Maven's strengths is the adherence to current best practices. Programmer tests running before a deliverable is created is one of the practices that Maven has stuck with from the beginning. I agree with dion's post that if someone is interested in this feature, provide a switch or some way to bypass the tests, but it should never be the default and probably not able to be set globally ( i.e. in build.properties, thus turning off tests for all maven projects you build ). But I would not recommend this choice. Another option would be to make sure that your tests are fast. I think that commons-collections has massive tests and they run in a very short amount of time. We've had to partition our tests into programmer tests ( what is generally thought of as unit tests ) and programmer-integration tests ( tests that depend on external systems like a db ). The integration tests wouldn't run at each build, but maybe after all jars have been built another pass is made running the integration tests. Another thing that I've noticed is the ant batch test task is slow, even slower when the test are forked. We've used TestSuite to help with speed problems also. I Hope this helps, jb On Mon, 2 Dec 2002, Matt Ho wrote: > Can I suggest that we remove the > > > > 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: > For additional commands, e-mail: > -- ===================================================================== Jeffrey D. Brekke jbrekke@wi.rr.com Wisconsin, USA brekke@apache.org ekkerbj@yahoo.com