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

On Wed, Jul 17, 2013 at 5:07 PM, Greg Taylor <greg.taylor_at_cunet.com> wrote:

> I manually marked them as derived in Eclipse resource properties (see attached). Using it for my own purposes has been very helpful in the past. :) Using svn:ignore means that everyone else on the project will have those files ignored since svn:ignore properties are checked into the repository. I'd rather have this just be a local thing.
>
> I think Subclipse just wants entire folders to be marked derived. It doesn't mark the project root as dirty if there's a derived folder in it, for example, so it's probably the presence of a derived resource in a managed folder that's causing it.

Marking a versioned resource as derived will not do anything, just as
trying to svn:ignore it will not do anything. These settings only
apply to unversioned items. There is nothing unusual about having
derived unversioned files in a managed folder. That is what happens
with .class files that are built in these folders.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3060699
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].