Mark Phippard wrote:
> Sebastian Hentschel <sebastian.hentschel@informatik.fh-gelsenkirchen.de>
> wrote on 01/27/2006 05:39:30 AM:
>
>
>> Here is an enhancement proposal.
>>
>> If i make bigger refactorings subclipse has no change to
>> detect an possible svn move. This is ok. But i think it
>> can be resolved easily.
>>
>> In Team Persipective we should select the original file(actually marked
>> as deletion) and the new file(actualliy marked as new) and
>> do something like
>>
>> Contextmenu(RightMouseButton)->Team->Mark as move.
>>
>> to mark the two opperations as an svn move.
>>
>> And now subclipse can handle it as svn move Operation.
>>
>> Hope to hear
>> what you think about my proposal
>>
>
> What would Mark as Move do? Subversion does not have a command that does
> this. If we run svn move, then Subversion would expect to do the move.
>
> Why are we not able to capture the refactoring in the first place? If the
> tool is properly respecting the Team API we ought to be notified. Usually
> the only problem that arises is when you do something in refactoring that
> the underlying Subversion API does not support. For example, I know there
> was a time when you could not copy/move something twice without a commit
> in between.
>
"There was a time"? Does this mean that it's currently possible? I just
tried renaming a file twice with the 1.2.3 commandline client, and it
complained. eg: "foo.txt" is committed, then I ran "svn mv foo.txt
bar.txt", followed by "svn mv bar.txt baz.txt":
svn: Use --force to override this restriction
svn: Move will not be attempted unless forced
svn: 'baz.txt' has local modifications
I'd love to learn how to make this work.
TIA,
Daniel Serodio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Feb 16 12:59:46 2006