Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 22201 invoked from network); 9 Aug 2004 13:27:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Aug 2004 13:27:58 -0000 Received: (qmail 27868 invoked by uid 500); 9 Aug 2004 13:27:15 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 27818 invoked by uid 500); 9 Aug 2004 13:27:14 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 27804 invoked by uid 99); 9 Aug 2004 13:27:14 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=FROM_ENDS_IN_NUMS X-Spam-Check-By: apache.org Received: from [66.33.216.24] (HELO smarty.dreamhost.com) (66.33.216.24) by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 09 Aug 2004 06:27:11 -0700 Received: from strange.dreamhost.com (strange.dreamhost.com [66.33.193.57]) by smarty.dreamhost.com (Postfix) with ESMTP id 6099B13F643 for ; Mon, 9 Aug 2004 06:27:10 -0700 (PDT) Received: by strange.dreamhost.com (Postfix, from userid 7734) id B4DB26A8ED; Mon, 9 Aug 2004 06:27:10 -0700 (PDT) Date: Mon, 9 Aug 2004 08:27:10 -0500 From: QM To: Tomcat Users List Subject: Re: [OFF TOPIC] J2EE/Tomcat Build Process Message-ID: <20040809132710.GA21932@strange.dreamhost.com> References: <5684A7E6FB10504393A2806C1F4C021003E0EDCF@orion.qas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5684A7E6FB10504393A2806C1F4C021003E0EDCF@orion.qas.com> User-Agent: Mutt/1.3.28i X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Mon, Aug 09, 2004 at 09:30:05AM +0100, Allistair Crossley wrote: : When I do a build, I am thinking that all source must be checked in, then a Get Latest Version, then run an Ant script to compile and generate a WAR for staging and production deployment. -as in, the nightly integration build? So far, so good. At one client, we had the build system send out a nastygram to the dev team if the nightly build failed. Sometimes the e-mails were followed by a morning visit to the offender's desk. That helped enforce the idea to only check in what worked. ;) : - should each developer have a locally installed TC rather than server based? You may as well, if you don't have a powerful enough shared dev server. The upside to the shared environment is that it's easier to catch "developer drift," when people start coloring outside the lines: several people notice sudden spikes/drops in system resources and can find the offender. : I would be very interested in others' development/deploy processes with mult-developer Tomcat environments to cross-check my ideas. I'll add a simple +1 to others' messages: you're on the right track. Put another way: what you're doing is pretty much standard practice in (well-run ;) multi-dev shops, so if it's wrong, you're in good company. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org