+1. I think I encountered this problem recently too :-/. The thing I noticed it a little bit late, and so I disconnected, then shared the project to commit a completely new version of the fucked up working copy. I do not know if it's subclipse fault at all, but maybe subclipe should call a refresh on the project root after a switch ?
Should we log an issue for that or aren't you able to reproduce this behaviour ?
Thanks.
> De : Beck Mischa [mailto:mischa.beck@rtc.ch]
> Envoyé : jeudi 9 novembre 2006 11:26
> À : users@subclipse.tigris.org
> Objet : [Subclipse-users] Refresh issue when using "switch"
>
> Hi
> I've remarked the following issue by using the "switch" function within the subclipse plugin:
> Eclipse 3.2.1 (Windows XP)
> Subclipse 1.1.8
> Happens with JavaSVN and JavaHL
>
> Problem description:
> If you have an existing working copy of a trunk and then switch to a branch the description behind the project correctly changes from "..[trunk..]" to "..[branch..]" (within the Java perspective), even if you check the project properties you can see that it is now linked to the branch. But within the subdirectories this will not be refreshed! If you check the file properties within the subdirectories you will see that they are still linked to the trunk! And even worse, if you do a commit then it will be commited to the trunk but the project was switched to the branch (you think you're working on the branch but your commits are made to the trunk)!
>
> So if you use the switch function you must do a manual refresh (F5) on the hole project -> then the subdirectories are refreshed correctly and all pathes are then linked to the branch.
>
> Best regards,
> Mischa
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Nov 9 12:50:52 2006