I was able to replicate this again, this time I was committing three
files all to the same project. I selected team -> synchronize then from
the synchronize view, I right clicked the project and selected "commit".
I typed a commit message, and clicked "ok". The files committed (I got
the email) however the synchronize view still shows uncommitted changes
and naturally the file decorations are still there. I am assuming it
will not be until I either do another team -> synch or a refresh of the
project that subclipse will take notice of the fact that these files
have been updated.
I must also note that when I committed, I had all three files open (plus
a couple of more) in the editor.
Does that help any? Any more questions?
-Zach
Mark Phippard wrote:
> Zach Bailey <zach.bailey@hannonhill.com> wrote on 06/28/2006 10:37:51 AM:
>
>> I am running Eclipse 3.2RC7 and Subclipse 1.1.2 with the JavaHL adapter.
>>
>> I have recently come across the following behavior:
>>
>> I open a single file for editing, say, "blah.java". I change a couple of
>
>> things...right click on the file and select "Team -> Commit". I enter a
>> commit comment and then commit the file successfully. However, my
>> Eclipse still shows the "uncommitted changes" decoration on this file.
>> If I wait a little while, keeping the file open I will eventually have
>> Eclipse tell me "the file has been changed on the file system. do you
>> wish to reload the file?".
>>
>> It seems that the commit operation is not telling Eclipse to
>> reload/refresh the file; apparently either subclipse or the subversion
>> adapter is doing something to the file or the file's metadata that is
>> not being immediately recognized by Eclipse. Either way, this is a minor
>
>> annoyance but an annoyance nonetheless.
>
> I tested (using same setup) and could not recreate. I tried both
> adapters. Decorator refreshes and I do not get the warning about being
> changed on disk.
>
> Are you using any features like svn:keywords which would cause SVN to
> change the file after you commit? That would at least explain the
> warning.
>
> Mark
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Jun 28 19:48:23 2006