Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 2893 invoked from network); 9 Mar 2004 23:43:15 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 9 Mar 2004 23:43:15 -0000 Received: (qmail 63265 invoked by uid 500); 9 Mar 2004 23:42:52 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 63234 invoked by uid 500); 9 Mar 2004 23:42:52 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 63221 invoked from network); 9 Mar 2004 23:42:52 -0000 Received: from unknown (HELO barrierb241.nike.com) (146.197.27.40) by daedalus.apache.org with SMTP; 9 Mar 2004 23:42:52 -0000 X-Server-Uuid: F122D6CD-24F0-4253-8986-549FB7942DF9 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: Guidance on build.xml to build dev/test/live with no changes Date: Tue, 9 Mar 2004 15:42:53 -0800 Message-ID: <200403092342.i29NgxhI022247@barrierb241.nike.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Guidance on build.xml to build dev/test/live with no changes Thread-Index: AcQGKtc+iz7+/cP9QcOcrk3SoQOBFQAA8dSA From: "Anderson, Rob (Global Trade)" To: "Ant Users List" X-OriginalArrivalTime: 09 Mar 2004 23:42:54.0218 (UTC) FILETIME=[3E08D6A0:01C40630] X-WSS-ID: 6C5089F4528261-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Actually, after reading your email again, I have some more suggestions. = I would still recommend using separate instances of tomcat, but I would = also suggest separating the "build" from the "deploy". So with separate = instances of tomcat you can produce a single war file that will run in = any (hopefully all) environment, with a single war-making target in your = build.xml. Then you could create a properties file for each environment = and create a deploy task that uses the properties defined for the = environment. -Rob Anderson > -----Original Message----- > From: Wendy Smoak [mailto:Wendy.Smoak@asu.edu] > Sent: Tuesday, March 09, 2004 3:05 PM > To: user@ant.apache.org > Subject: Guidance on build.xml to build dev/test/live with no changes >=20 >=20 >=20 > I'm trying to cut down on the amount of editing files before=20 > building a > live version of my project as opposed to a test or=20 > development version. > I learned how to use @token@ in files and then replace them from the > contents of a .properties file, so that solved most of it (location of > log files, for example). >=20 > The last thing I'm stuck on is that I have in build.xml: >=20 > >=20 > And it gets used for such things as: >=20 > > > > > >=20 > Which in turn controls the name of the context in Tomcat and=20 > the URL you > use to access the web application once the .war file gets deployed >=20 > Do I just end up with three properties (context-test, context-dev, > context-live) and three matching 'war' targets? Or is there a better > way? >=20 > Thanks, >=20 > --=20 > Wendy Smoak > Application Systems Analyst, Sr. > ASU IA Information Resources Management=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