Martin Cooper <[EMAIL PROTECTED]> wrote: > Other issues with keeping Eclipse files in our repo: > > 1) The expectation would be that they would be kept up to date. If a > particular committer doesn't use Eclipse, I don't think it's fair to > expect them to keep Eclipse config files up to date when they make > changes elsewhere.
In the cayenne project, the .classpath and .project files are stored in /cayenne/contrib/ide/eclipse/. If you want to use them, you just copy them into your root project directory first. At least under Eclipse, these files don't change very frequently (.classpath when project dependency changes, .project never changes.). If you don't use a particular editor, you don't need to mess with them. Let the people using that particular editor update them. It's the same thing that's going to happen even if the config files are not in the repo. The only difference is that it gives a starting point (and will generally be up-to-date for a particular editor if active committers are using it). -Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
