[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] subclipse enhancement

From: Sebastian Sickelmann <sebastian.sickelmann_at_four2b.de>
Date: 2006-02-09 08:55:17 CET

>
> From: Mark Phippard <markp@softlanding.com>
> Date: Fri, 27 Jan 2006 08:32:26 -0500
> Content-Type: text/plain; charset="US-ASCII"
> Subject: [Subclipse-users] subclipse enhancement
>
>
> 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.
>
It marks that the two files(the files marks with - and the file marked
with +) are sematically the same
file. And that an 'move'(or 'copy' and 'delete') instead von an 'add'
and 'delete' should be done.
> 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.
>
subclipse captures the refactoring(i.e. move to another package) very
well, and creates an 'move'(or 'copy' and 'delete').
But if i make additionally refactorings(i.e. extract some code to a
method, or create a new Method) it
seems to loose the 'move-nature' of the first refactoring.
An Mark as move would mark the two files explicit to an move. subclipse
can do a copy (oldfilename to new filename)
and commit the latest filecontent to the new filename.
But it should be done in one transaction to keep the repository consistent.
Or is it not possible to move an file and change its content in the same
transaction?

Regards
Sebastian
> Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Feb 9 09:09:41 2006

This is an archived mail posted to the Subclipse Users mailing list.