[news.eclipse.newcomer] Re: Workspaces and CVS

[duncan@xxxxxxxxxxxx (dkrebs)]

> First, is it possible to set up user specific privileges that limits some 
> people's abilities to check in possible changes to .classpath or .project 
> files, i.e. perhaps a user changed certain debug preferences that we don't 
> want carried back into the repository?

I'm sure it is but that sounds like something that would have to be 
configured inside the CVS server and not in eclipse. For example I'm sure 
you could create two cvs logins. One that lets users commit .project and 
class files and another account that does not. 

> One idea we had for getting around that is branching off if someone needs to 
> make changes to the workspace environment and then merging back once they 
> finished what they are doing.  So the next question, is it possible to merge 
> ..classpath and .project files that have been branched?  Is it a good idea 
to 
> do so?

Sounds too messy. I also would not really worry about it too much because 
a lot of workspace specific configuration stuff including debugging is 
stored in the users local workspace and not in the .classpath and .proejct 
files. I'd suggest starting by committing one project to the repository 
and have your developers get together and walk through the process of 
checking out projects and see what breaks.