On Tue, 2002-03-26 at 10:15, Chris Shenton wrote: > "Gareth Coltman" <[EMAIL PROTECTED]> writes: > > > Alternatively a method we used was to use tokens like > > > > @dbdriver@ > > > > in the tr.props file and have a seperate build.properties file outside of > > cvs, e.g. > > > > dbdriver=Oracle > > > > Then use ant to filter the tr.props fill and fill in the tokens from the > > build.props at build time. > > Is it possible to make a decision on how to populate this at run-time, > like based on the hostname? That way I wouldn't have to have a > separate mini-config file for each host.
I do have something for this but I have to dig it out. I made an sample installer for Tambora that used a small configuration file to generate the target db stuff. I'm planning on integrating it into the TDK, but no time as yet. This is definitely possible, actually creating the db on the client machine automatically. > We take our source from CVS then wipe-and-install on the target QA > systems where our DB also has different configs. After that, we > wipe-and-install into our Production systems, where there's yet > another config. It would be real nice if we didn't have to tweak > these DB-config files each time but could let Ant make a decision > based on hostname or something else machine-specific. > > Thanks. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
