How to maintain base files for development environment central while allowing people to change their
Posted
by Ittai
on Stack Overflow
See other posts from Stack Overflow
or by Ittai
Published on 2010-04-26T07:07:14Z
Indexed on
2010/04/26
7:13 UTC
Read the original article
Hit count: 312
Hi, what I'd like to do is have files in a central location so that when I add people to my development team they can see the base version of these files but meanwhile have the ability for the rest of the team to work with their own local version. I know I can just put the files in source-control (we use Tortoiese-SVN) and have my team change the local versions but I'd rather not as the exclamation mark signaling the file has been changed and needs to be committed, quite frankly, irritates me greatly. I'll give two examples of what I mean:
- We use quite a few build.xml files which relate to a single properties files which contains many definitions. Some of them can be different between team-members (mainly temporary working directories) and I'd like a new team-member to have the ability to get the properties file with the base config but change it if they wish.
- Have the eclipse settings file in the SVN so that when a new team-member joins they can just retrieve the files from the server and have a base system running. If they wish they will be able to change some of these settings.
Thanks, Ittai
© Stack Overflow or respective owner