On 5/4/07, Tony Herstell <firstname.lastname@example.org> wrote:
> I have had to destroy and re-create my repository numerous times after
> It appears when I use MyEclipe to move a directory then I introduce some
> sort of confusion with subclipse.
> I "think" that it does not flag a delete to the directory so you end up with
> both the new and old directories known about.
> The only solution I have found is to destroy the repository and re-create
Why? Certainly checkout would resolve any problems.
> I MUST be doing something stupid, but I can't figure out what.
> click over a directory (package)
> click rename...
> Give a new name
> Then when you come to team->synch it appears to work... but subsequent to
> that you get all sorts of problems!
> It ONCE fixed itself and that was when I ONCE saw a file with a little red
> cross on it (delete?) go though as an update... never seen it again though.
Rename/move in Subversion (the svn move) command is implemented
internally as a copy + delete. When a folder is deleted, you still
see it until it is committed. So this part all sounds right.
When you commit or synchronize you would want to be sure to do it from
a parent folder so that you could commit the copy and delete in the
Note, that this is Subversion, not Subclipse, that does it this way.
We execute the svn move command, and this is what happens. You should
be able to see this in the Console view.
One thing to watch out for is that Subversion has a limitation that an
item cannot be moved twice without a commit in between the moves.
This is resolved in the next release of Subversion. In the meantime,
be aware of that as it can lead to further problems.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri May 4 23:20:57 2007