"Jon Skeet" <Jon.Skeet@clearswift.com> wrote on 02/17/2006 05:04:41 AM:
> I've just tried two experiments with the Refactor/Move command in
> Eclipse. The first moved an item between two projects in the same
> repository, while the second moved items between two different
> repositories.
>
> The first worked flawlessly - a single transaction created a copy and
> deleted the old version.
>
> The second didn't work at all - Subversion (understandably) complained
> that you can't copy an item from one repository to another.
>
> It would be nice if the second case were handled better. If Subclipse
> could detect that the repositories are different, it could delete in one
> repository and add the item (as a new file) into the old one. This would
> require confirmation on the part of the user that they understood that
> history would be lost, but I can see it being useful. Of course, the
> same functionality is "manually" available through copy/paste/delete,
> but then the rest of Eclipse's refactoring support is lost.
>
> Does this sound like a reasonable feature request (albeit a low priority
> one)?
The request is not unreasonable. If you want to enter an issue, feel
free. Be aware that implementing the feature is not necessarily as easy
it sounds. I do not know if it has been committed to trunk yet, but I
think I have seen Subversion mailing list discussions about providing some
basic API support for this, which might help.
Mark
_____________________________________________________________________________
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 Fri Feb 17 15:21:20 2006