I do not think that you will need to make the second F5, but for this reason we added the command Team> Refresh / Cleanup.
With pre-SVN 1.7.x, any change in the files caused by the working copy is released in all hidden .svn folders for the change. When you press F5 in Eclipse, it will see these modified files and disable the notifications that Subclipse will see and use to update the scenery.
With SVN 1.7, all this information is consolidated in one place, and it looks like it does not even live inside your Eclipse project folder. Thus, F5 in Eclipse effectively does nothing, because files on the file system that Eclipse does not see have been changed. Eclipse does not send any notifications.
The Team> Refresh / Cleanup parameter invokes the same Eclipse action as F5, but also triggers an explicit update of the cached SVN information, regardless of whether Eclipse sees any changes.
Mark phippard
source share