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

Re: [Subclipse-users] Subclipse shows folder as dirty when the only modified resources are marked derived

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 17 Jul 2013 16:58:38 -0400

On Wed, Jul 17, 2013 at 4:48 PM, Greg Taylor <greg.taylor_at_cunet.com> wrote:
> I used to use this technique to modify shared config files so that they're not checked in again. E.g. log config, database connection template files, etc. You check out the project and get the default configuration, but then modify it to suit your preferences and then mark it derived so that you don't check it back in and it doesn't show up as a local change. Worked great! Unfortunately, since a change to Subclipse in the last 8 months or so, now the folders show up as dirty, even if the only changed resources inside are marked derived. See attached - the schema and web folders are clean and show nothing to commit, but they appear dirty. That's because there are a couple of local changes to files that I've then marked derived.
> The old behaviour was totally awesome and the new behaviour drives me nuts because I keep thinking I've changed stuff in those folders when I haven't. :( Any way I can bring back the old behaviour without reverting to 1.7 or something? Is this a bug? I'm going to gouge out my eyeballs soon. Please save me!

Nothing has changed in Subclipse. I would guess they are not Derived
any more. Derived is not meant as a user-editable property. Why not
just use svn:ignore settings to ignore the files?

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2013-07-17 22:58:45 CEST

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.