That is a bug. It was always updating to HEAD which is not correct
either. I am trying to update to the revision shown in the view. It uses
the highest revision number in the current selections. I think the
problem is that it does not account for the idea of having multiple
projects from different repositories in the view,
I will have to test that and see what I can do, I would guess that
selecting one project at a time would work.
Thanks
Jörg Eichhorn <eichhorn@ponton-consulting.de> wrote on 01/10/2006 04:18:53
PM:
> Hello,
>
> i've just updated subclipse to version 0.9.103 running with eclipse
3.1.1
> on WinXP-SP2.
> I wanted to update several projects which are each in a separate https
> repository (server uses
> subversion 1.3.0). I've selected synchronize in the team context menu
after
> selecting the following
> 5 projects, looked at the changes, collapsed the treeview in the
> synchronize view, select all 5 projects and clicked on 'Update' in the
team
> context menu. The revision number before the update were only a few
> revisions below of the highest revision of each project.
>
> Higest revision numers in checked-out path of the projects:
> project1 58
> project2 385
> project3 6888
> project4 373
> project5 580
>
>
> The following happened:
>
> update -r 373 D:/src/workspace/project2
> --> to rev 373
> update -r 373 D:/src/workspace/project1
> --> error because rev 373 is not available for this project
> update -r 58 D:/src/workspace/project2
> --> to rev 58
> update -r 373 D:/src/workspace/project4
> --> to rev 373
> update -r 58 D:/src/workspace/project1
> --> to rev 58
> update -r 580 D:/src/workspace/project2
> --> error because rev 580 is not available for this project
> update -r 373 D:/src/workspace/project3
> --> to rev 373
> update -r 58 D:/src/workspace/project4
> --> to rev 58
> update -r 580 D:/src/workspace/project1
> --> error because rev 580 is not available for this project
> update -r 6888 D:/src/workspace/project2
> --> error because rev 6888 is not available for this project
> update -r 373 D:/src/workspace/ebXMLPipe-Distribution
> --> to rev 373
> update -r 580 D:/src/workspace/project4
> --> error because rev 580 is not available for this project
> update -r 6888 D:/src/workspace/project1
> --> error because rev 6888 is not available for this project
> update -r 385 D:/src/workspace/project2
> --> to rev 385
> update -r 58 D:/src/workspace/project3
> --> to rev 58
> update -r 6888 D:/src/workspace/project4
> --> error because rev 6888 is not available for this project
> update -r 385 D:/src/workspace/project1
> --> error because rev 385 is not available for this project
> update -r 385 D:/src/workspace/project4
> --> error because rev 385 is not available for this project
> update -r 580 D:/src/workspace/project3
> --> to rev 580
>
> ... aborted because of strange behavior.
>
>
> I'm quite sure that the same worked with subclipse 0.9.37.
> Could this be a subclipse bug, or is this a handling error.
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jan 10 22:22:57 2006