Thanks for the quick reply, Mark. The synchronize view is empty when I
synch, so it is running, and when I right-click->show history, I can see the
latest revision and grab it. I would really like to know what the
difference is between running svn commit on the server, and commiting from
subclipse. Any idea why the server commit gives me the latest revision
number in the synchronize view, but not the subclipse commit?
Thx again.
-Eli
On 2/28/07, Mark Phippard <markphip@gmail.com> wrote:
>
> On 2/28/07, eli bird <elibird@gmail.com> wrote
> >
> > Using Subclipse1.2 with Eclipse3.2.1, and Subversion1.4.2. I'm having a
> > problem getting the right revision # from the Synchronize view. After my
> > partner commits a change, and I hit the synchronize button, the file he has
> > commited appears, but with my current revision number, not the latest
> > revision from the repository. Therefore when I right-click on the file and
> > select update, I get the message 'At revision 14' when I want to update to
> > revision 15. What is more curious is that when I edit a file on the server
> > and commit the change, the correct revision number shows up in the
> > synchronize view and I can update no problem. Is there a way to always get
> > the HEAD revision from the synchronize view? If not, I could work around
> > this problem by always updating from the Navigator view, since that grabs
> > the HEAD revision each time, but I would like to use the Synchronize view if
> > I can get it working properly. Maybe it *is* working properly?
>
>
> Synchronize always goes against HEAD. Are you sure you did not already
> have the view loaded and then it did not refresh/re-run? Update from the
> Synch view will only update to the revision you see in the view. This is so
> if you spend a long time doing compares and looking at the changes you do
> not then update and potentially get a different version than you were
> looking at.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
Received on Wed Feb 28 22:20:23 2007