Ant is the key to solving this problem. Unfortunately I don't have the gift of being able to elegantly summarize the solution for you, but I will tell you that I rely on Ant to solve this problem for me, and it works! The key is to have multiple property file sets, and work out a way to specify which set is sourced at build time. Then, let the properties do the work for you. Hopefully this will make sense and be helpful.

Troy

Kevin Tung wrote:

How does everyone manage different deployment configurations?

Let's say your webapp needs to run in various environments.. for example
dev, staging and production.  Each environment has its own database
connection info and third party SOAP endpoints.. etc.

What is a good way to automate (at least partly) the management of these
configurations so that..

* The process of promoting code from dev to staging/production will trigger
a correct change of configuration info.
* The configuration info can be stored in a code repository for history
logging and accountability.

I've been doing this mostly manually, but there has to be a better way..  I
would love to hear about your approaches.

Kevin


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]






--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to