On 3/22/07, Justin Erenkrantz <firstname.lastname@example.org> wrote:
> On 3/23/07, Karl Fogel <email@example.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
> > 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
I do not think it is a matter of feeling special. I want people to be able
to use Eclipse to work with Subversion. Do we all have to pass a secret
emacs test to contribute? Eclipse is rigid on where the files need to be.
If it wasn't this would be a non-issue and we would either stick the files
somewhere else, or not at all.
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.
This is not really true. Part of the reason I wanted to commit these files
is so that we could commit the Subversion project's preferences, not mine.
I just want to be able to submit a fix without being bitched at because it
has a friggin tab character in it or the braces are not to someone's
liking. I took the time to look at the code styles and set the Eclipse
preferences for the project so that it would format the code according to
those preferences. On the Java related files, there is not a single
preference that would need to be changed, ever, unless we decided to change
something about our style or Eclipse added some even more refined
preferences for getting it just right. Those changes should be reviewed and
approved/committed like any other change to a file in the repository. I
cannot make the same claim for the CDT files because I have not completely
set that up yet and I also do not know how well it abstracts platform
differences in those files. The JDT files do this well.
My vote is a very very strong 'no'. -- justin
OK, new proposal.
1) You let me add all of these files to the svn:ignore property on trunk.
One of main reasons for wanting the files committed is that they are a real
nuisance when they are unversioned and not ignored.
2) Optionally, I can also add an eclipse-project folder under
developer-resources. Users could either use this as a way to checkout in
Eclipse and have things setup, or at a minimum, it would be a place to store
these files and a readme so that someone can use them to manually setup an
environment if they want to use Eclipse. I think that the code formatting
preferences, at least, would be useful to some people.
This would all be fine with me.
Received on Fri Mar 23 02:35:45 2007