> G> It sounds like the refactoring that led to this problem is like
renaming a
> G> Java package, which is a very significant operation.
> BTW, here is a problem. To rename Java or PErl package your need to
> MOVE it and CHANGE FILE. And these operations could not be performed in
> ONE step (revision) now :( So, atomic renaming of package is
> impossible...
>
> Are here any plans to remove this restriction in future? FS Dump
> can contain two entries for one file (node) in one revision : copy
> and change after that. So, it seems to be possible on low level. But
> svn complains about restricted operation :(
Please note that a move is possible to be done just in a work area
without contacting a server. So, if you're using Eclipse or some other tool
to help with the refactoring, all of the changes will be made just in your
work area. Only when you're done will the changes be committed, atomically,
to the server.
The earlier suggestion to do this with a URL-to-URL move doesn't really
apply here, because the revision that creates wouldn't compile until all
affected files were modified once again to apply the new package name.
Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 28 10:56:21 2003