[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Unversioned folder marker problem.

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-01-31 15:44:16 CET

"Rob Masargo" <rmasargo@hotmail.com> wrote on 01/30/2006 08:35:16 AM:

> I just upgraded my Subclipse SVN client and have noticed something that
I
> thought was a bug, but after further research, it turned out to be a
change
> in feature. According to your log, as of December 1st, "When a folder
> contains unversioned (and unignored) resources, decorate the folder as
> modified. This is how the CVS plugin handles it.". This is also the
reason
> why I don't use CVS and recommend the use of Subclipse to others. Most
of
> the time, many software creates many temporary items - especially when
you
> are mixing different programming languages within one Eclipse Java
project.
> These temporary items and binaries should not be checked in even though
they
> are created in the same folder. One might also want to disassociate
files
> that has been checked out (e.g. properties files) to make customization.
 
> Having a "modified" marker on these "unversioned" files renders the
> "modified" status pretty useless to me because almost ALL folder now has
a
> star. :(
>
> I do realize that I can add individual files to the ignore list, but
that
> would waste a lot more time when certain program create new logs,
temporary
> files, or other file not relevant to the repository. My suggestion is
> either bring back good old version feature (before 0.9.100) or add a
check
> box to give the end user a choice. Thank you for your attention.

I am sorry that this feature change doesn't work as well for you as the
old method, but I am convinced that the way it now works is the right way.
 I also do not like adding preferences for every posible feature and in
this case, at the level code this feature is implemented a preference
would be difficult. We would have to make significant changes in some of
the base code to make this configurable.

The svn:ignore feature is very easy to use and supports wildcards. Eclipse
also has an Ignored resource option that we honor. The svn:ignore option
would be the better way to go since other Subversion clients would
automatically use it as well.

The other option would be to isolates these items in their own folders, so
that you just have to ignore the folder.

I know you have thought of all of these things before, I just do not think
there is any other way to do it. Another advantage that using svn:ignore
is going to give you is that these items are not going to show up in the
Synch view or the Commit dialog and you do not have to worry about ever
accidentally committing them.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jan 31 16:01:30 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.