> -----Original Message----- > From: Scott Eade [mailto:[EMAIL PROTECTED]] [...] > I am curious as to how others deal with this issue - have you > got a better solution that you would like to share?
Not better, just different. I have a reference tr.props for production and each subproject also has its own tr.props. Obviously the project that is on top of the reference hierarchy will have its tr.props closest to the production one except of course for optimization things...caching, reloading etc...this is kind of the same for the app server configuration anyway. Include could indeed simplify the work by making them more readable, but I use Ant for deployment that modifies the props according to what the user choose as properties (database, etc...) Ant is called from an Installshield app (with nice wizard screens :) and it also allows the deployment to be run from the command line (always useful for batch processing). When doing that it is somewhat better for me to use a single config file. Stephane -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
