ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anderson, Rob (Global Trade)" <>
Subject RE: Guidance on build.xml to build dev/test/live with no changes
Date Tue, 09 Mar 2004 23:42:53 GMT
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 []
> Sent: Tuesday, March 09, 2004 3:05 PM
> To:
> Subject: Guidance on build.xml to build dev/test/live with no changes
> I'm trying to cut down on the amount of editing files before 
> building a
> live version of my project as opposed to a test or 
> 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).
> The last thing I'm stuck on is that I have in build.xml:
>    <property name="context" value="coltest" />
> And it gets used for such things as:
>   <target name="war" depends="clean,init,compile,props-war">
>     <zip destfile="${dist}/${context}.war" compress="false">
>       <zipfileset dir="webapp"     prefix=""/>
>     </zip>
>   </target>
> Which in turn controls the name of the context in Tomcat and 
> the URL you
> use to access the web application once the .war file gets deployed
> 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?
> Thanks,
> -- 
> Wendy Smoak
> Application Systems Analyst, Sr.
> ASU IA Information Resources Management 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message