-----Original Message-----
From: Johannes Schneider [mailto:[EMAIL PROTECTED]]
Sent: 04 March 2002 16:46
> we use CVS to controll a project. We are 4 developers at the moment and
> everybody uses different configuration-files (log4j.properties, ...).
> We would like to hold a "basic"-version of those files in the
cvs-repository
> but if one updates or commits the hole tree we run into some troubles...
> How do u handle individuall configuration files?
I've handled this by making the property file names configurable, eg as a
command line argument to the build process. We then keep the standard
uat/prod etc config files in cvs. Developers then have their own versions
but with a different name. So long as they don't try and add them to the
respository cvs ignores them, just displaying a question mark next to them
when you run an update.
----------------------------------------------------------------------
If you have received this e-mail in error or wish to read our e-mail
disclaimer statement and monitoring policy, please refer to
http://www.drkw.com/disc/email/ or contact the sender.
----------------------------------------------------------------------
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
