Re: [Subclipse-users] Why doI have upcoming changes after a commit?(single user)

jambalaya <incog_83@wp.pl> wrote on 10/08/2006 10:40:47 AM:

> Immediately afterwards i synchronize again, and I hav upcoming chamges -
all
> the dirs which contained the files I've just commited. Why does it
happen? I
> have the most recent working copy, don't I? Is this a bug or am I doing
> something wrong? The problem existed even if I dodn't fiddle with the
bin
> and other project specific files. Please answer.

It is not a bug, it is a feature. Literally. There is an option on the
Synch view (and in preferences) to "Show Out of Date" folders. This is on
by default. When you commit a file, all parent folders going all the way
back to the repository root have their revision bumped in the repository.
However, the folder in your WC is not update by committing a file. It
sill needs to be update to move up to that version. So the Synch view is
showing you when your local folders are out of date with the repository.

The real issue is that if your local folder is not at the HEAD revision,
then certain operations such as setting folder properties as well as many
refactoring operations will not allow you to commit the change until you
have updated. See this FAQ:

http://subclipse.tigris.org/faq.html#out-of-date

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Oct 8 20:37:26 2006