Jay Sachs <jay.sachs@riskmetrics.com> wrote on 10/18/2006 07:37:58 AM:
> "Me too". I'll try to reconstruct what happened. I had a folder
structure
> like
>
> proj/src/java/a/b/c
>
> with Foo.java locally changed, and Bar.java a new addition. Furthermore,
> directories from "proj" down to "b" (I think) were out of date with
respect
> to the repository. I committed Foo.java and Bar.java. Synchronize still
> showed incoming changes on the folders, so I chose "updated". This
actually
> undid the change to Foo.java and removed Bar.java, and the synchronize
> window was clear. However, I was momentarily very concerned, but when I
> checked the console window, I was reassured that the commits at least
went
> in and would be retrievable. In fact, a subsequent "update" in the
Package
> Explorer pulled in my just-committed changes. So I'm guessing that the
> synchronize picked up the revision difference on the top folder, but
after
> the commit, didn't update its notion of the latest revision.
This is because update will update to the revision shown in the view. At
the time you did Synch, this was the correct revision, but once you did a
commit, it was now "stale". You should either be doing update before
commit or refreshing the synch view after a commit so that the newly
created revision is reflected in the incoming changes. I will probably
need to look into doing this automatically.
Finally, if you are using JavaSVN, there is currently an issue where after
doing an update you need to refresh your project to get all of the updates
to the folder revisions registered.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Oct 18 14:40:32 2006