Re: [Subclipse-users] False update markers and keyword expansion

"Bas Cancrinus" <BCancrinus@iprofs.nl> wrote on 10/13/2006 08:37:20 AM:

> My team has the following problem with Subclipse 1.1.6/1.1.7 (Eclipse
3.2.x)
> when keyword expansion is turned on:
>
> - Pre-condition: a Subversion-project is checked out in the workspace.
>
> - Steps to reproduce:
> 1. Change a file in the project;
> 2. Commit the file with Subclipse;
> 3. Refresh the Team->Synchronize view;
>
> - Result: all parent directories of the commited file are marked for
update.
>
> Is this a known issue? If so, what can we do to prevent Subclipse from
> marking the parent directories for update?

This has nothing to do with keyword expansion. It is normal expected
behavior. See this from the archvives:

http://subclipse.tigris.org/servlets/ReadMsg?list=users&msgNo=8287

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Oct 13 14:40:57 2006