it's doable, some of my teammates use that method, but it's a pain in
the butt because you basically have to create 3 WARs per release (one
for each target). considering a struts/hibernate/spring/xFire
application is about 30mb in 3rd party jars, that's a lot of space. ok
HD space is cheap, but it's still no excuse for poor procedure.
To do it you would basically create different build targets in your ant
script, with each one using custom props from your build.props file, eg
- so you would have targets dev/test/prod/all, running all would build
wars for dev, test & prod. you use a <replace> tag to replace a
pre-formatted pattern like ##db_user##, ##db_pwd## etc in your
deployment descriptor with the target details. it's a crappy hack for
bad programmers.
Len Popp wrote:
How do you use a build.properties file to define a JNDI resource? Or
do you create JDBC connections a different way?
--
Matthew Kerle
IT Consultant
Canberra, Australia
Mobile: +61404 096 863
Email : [EMAIL PROTECTED]
Web : http://threebrightlights.blogspot.com/
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
