Simple!
Cut the relevant database properties out of TR.props and put them into another file, say DB.properties. Add the following line to the TR.props file: include=DB.properties Use a different DB.properties file depending on your needed configuration. Skip > -----Original Message----- > From: Jesse Chen [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 25, 2002 9:03 PM > To: Turbine Users List > Subject: config layers > > > Hi, > > We have 2 teams that are currently developing on a shared > codebase using > Turbine2.1 in CVS in opposite parts of the world. > Unfortunately, the DB > settings need to be different for each team due to network > infrastructure > issues. > > I was wondering if there was an elegant way to point the > Database Settings > properties in TurbineResources.properties to an alternate > properties file > (ie: conf/localDev.properties) without having to extend the > TurbineResource > classes? This way, we can share config settings on everything > else except > the DB settings, which can be managed locally. > > thx, > > J > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
