Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Date: Wed, 10 Mar 2004 07:54:45 -0700
From: Wendy Smoak <Wendy.Smoak@asu.edu>
Subject: RE: Guidance on build.xml to build dev/test/live with no changes
To: Ant Users List <user@ant.apache.org>
Message-id: <A7AF1AE70A8C124593A1AC831EFE46FE0399D746@ex3.asurite.ad.asu.edu>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Thread-Topic: Guidance on build.xml to build dev/test/live with no changes
Thread-Index: AcQGKtc+iz7+/cP9QcOcrk3SoQOBFQAA8dSAACAB3iA=
content-class: urn:content-classes:message

> From: Anderson, Rob (Global Trade) [mailto:Rob.Anderson@nike.com]=20
> Actually, after reading your email again, I have some more=20
> suggestions. I would still recommend using separate instances=20
> of tomcat, but I would also suggest separating the "build"=20
> from the "deploy".

Separate Tomcat instances aren't an option-- there's only one production
web server, and I need to run live, test and development versions of
this webapp on it under different context names.  Actual development is
done on my desktop, there I could run multiple Tomcats, but that doesn't
really fix the problem.

Moving from test to live involves copying the entire source tree and
renaming the directory, then editing some text files, the .properties
file that says which database account to use, and build.xml to change
the context name.

It looks like to get away from the editing I'll run 'ant war-live' or
'ant war-test', etc.

--=20
Wendy Smoak
Application Systems Analyst, Sr.
ASU IA Information Resources Management

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org