Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 99057 invoked from network); 12 Jul 2005 19:02:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jul 2005 19:02:37 -0000 Received: (qmail 36136 invoked by uid 500); 12 Jul 2005 19:02:29 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 36099 invoked by uid 500); 12 Jul 2005 19:02:28 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 36085 invoked by uid 99); 12 Jul 2005 19:02:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jul 2005 12:02:28 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [146.197.27.40] (HELO barrierb241.nike.com) (146.197.27.40) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jul 2005 12:02:25 -0700 X-Server-Uuid: BDE2CC8B-9671-48D4-9A25-CA756DA0A621 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: Doing patch builds Date: Tue, 12 Jul 2005 12:02:14 -0700 Message-ID: <200507121902.j6CJ2Pka020834@barrierb241.nike.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Doing patch builds Thread-Index: AcWG/ZJlRXg5kP9ATOKjVvEabiCLxAAFhPEg From: "Anderson, Rob (Global Trade)" To: "Ant Users List" X-OriginalArrivalTime: 12 Jul 2005 19:02:16.0032 (UTC) FILETIME=[381B0E00:01C58714] X-WSS-ID: 6ECACC311U4484771-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I would discourage you from persuing a patch build solution. I would = suggest that a patch build be treated as an entire new build. There are = several advantages to this approach. 1. The build and deployment process is always the same. 2. The person doing the build and deploy does not need to know what has = changed, and therefore will not need to do anything differently in order = to deploy the build. 3. The build will move through your environments as a single unit. This = will ensure that the changes are tested and deployed together with their = dependecies, etc. -Rob A > -----Original Message----- > From: S I [mailto:xiamak@hotmail.com] > Sent: Tuesday, July 12, 2005 9:19 AM > To: user@ant.apache.org > Subject: Doing patch builds >=20 >=20 > Hi >=20 > I was hoping someone could put me on the right track please. >=20 > I finally automated my whole build and deployment as well as=20 > writing code to=20 > handle branch builds. Now I need to write code to handle=20 > patch builds. =20 > This is when the developers hand over couple of modified=20 > files which need to=20 > be compiled, packaged, and delivered to our production to be=20 > deployed (in a=20 > .war file) to the live site. >=20 > I'm not sure how to go about doing a build that looks into=20 > CVS for the=20 > changed files, compares them to a list sent by the=20 > developers, and then it=20 > parses out their corresponding .class & .jar files or=20 > deliverables and=20 > packages them into a .war file? This brings me to my next=20 > question: Does=20 > anyone know if Tomcat needs the complete war file to explode=20 > or could it=20 > just explode a war file which contains only the latest=20 > modified files and=20 > replace the files on the live site? Any ideas? >=20 > Thank you >=20 > Steven >=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > For additional commands, e-mail: user-help@ant.apache.org >=20 >=20 >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org