On 3/23/07, Karl Fogel <kfogel@red-bean.com> wrote:
> I'd recommend posting a very short mail here, listing just the file
> names, in the body of the message not in a patch :-). Here, let's
> save some time...
>
> http://svn.collab.net/repos/svn/trunk/.cdtproject
> http://svn.collab.net/repos/svn/trunk/.project
> http://svn.collab.net/repos/svn/trunk/.classpath
> http://svn.collab.net/repos/svn/trunk/.settings/org.eclipse.jdt.core.prefs
> http://svn.collab.net/repos/svn/trunk/.settings/org.eclipse.jdt.ui.prefs
> http://svn.collab.net/repos/svn/trunk/.settings/org.eclipse.cdt.core.prefs
>
> That's it, right?
I have other SVN-using projects that I'm involved with that do this
and I *hate* it. I don't know why Eclipse users feel so special that
they *have* to commit everything that their IDE creates into the
repository.
You also realize that every person who now decides to open up SVN
under Eclipse will get these files changed - as they aren't treated as
read-only by Eclipse - in essence, everyone would get Mark's
preferences when they first open up Eclipse under the CDT (or JDT for
JavaHL) - but if they tweak the Preferences and other settings, bam -
these files change - so folks would now get those files marked as
changed locally. Eww. Eww. Eww. We shouldn't be committing
tool-generated files into our repository! This is the largest problem
in practice with these files in our projects that use this - no one
agrees on a JVM or version of Eclipse - so the file is always getting
tweaked unnecessarily - the end result is that we have to often
recommend that people just ignore those files when they are modified
and not check them in even though SVN shows them as modified. Unclean
to n'th degree.
My vote is a very very strong 'no'. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 23 01:36:39 2007