RE: [Subclipse-users] No history after refactoring

Thank you Trevor,

I like subversion but this is a design problem.

Zsolt

  _____

From: Trevor Whitlock [mailto:twhitlock@gmail.com]
Sent: Wednesday, April 05, 2006 4:49 PM
To: users@subclipse.tigris.org
Subject: Re: [Subclipse-users] No history after refactoring

The problem here is that you did two moves before a commit. Once was a
move, and once was a re-name. They are both done the same way in
subversion. However, the first one did a copy+delete, and the second one
did a copy+delete also, however the file that it copied didn't exist in the
repository, so it didn't have any history to copy. If you are moving or
renaming files and want to keep the history you should commit them after
each move/rename. This will preserve the history.

-Trevor

On 4/5/06, Greg Irvine <greg.irvine@thalesatm.com> wrote:

I hate to interject here, but it definitely supports renaming.

You can see from the command below, an svn log on the file
"config_tipp.xml", which was prior to the latest version (as seen in the
delivery comments), called tipp_config.xml and the history has picked up all
of the history prior to the rename.

If working from the command line you need to ensure you use "svn move".
Team->Rename in eclipse has worked as a move for a long time (even though
the svn console says add+delete: this is also said on the command line!).

There was and may still be a problem in subclipse regarding showing the
history of a file that has been MOVED to a different package. It doesn't
seem to correctly pick up all of the history.

 [cruise@lolek workspace]$ svn log config_tipp.xml

------------------------------------------------------------------------

r11610 | cruise | 2006-03-30 15:25:55 +1000 (Thu, 30 Mar 2006) | 2 lines

move **_config.xml to config_**.xml. creation of validation config and
build files.

------------------------------------------------------------------------

r11388 | cruise | 2006-03-15 10:16:09 +1100 (Wed, 15 Mar 2006) | 2 lines

Updates to cruise build configuration.

------------------------------------------------------------------------

I even did a log on a file in a new branch that shows the history of a
particular file all the way back to the beginning of the project. That
branch is based upon another branch from another branch from the trunk.
Seems to work ok here.

-----Original Message-----
From: Zsolt [mailto:zkoppanylist@intland.com]
Sent: Wednesday, 5 April 2006 3:35 PM
To: users@subclipse.tigris.org

Subject: RE: [Subclipse-users] No history after refactoring

It is onchecked. I also executed svn log and that doesn't provide history

information (before the rename) either.

I would say: subversion DOES NOT support renaming, it is just a marketing

issue.

Zsolt

>-----Original Message-----

>From: Mark Phippard [mailto:markp@softlanding.com
<mailto:markp@softlanding.com> ]

>Sent: Tuesday, April 04, 2006 4:05 PM

>To: users@subclipse.tigris.org

>Subject: Re: [Subclipse-users] No history after refactoring

>

>"Zsolt" <zkoppanylist@intland.com > wrote on 04/04/2006 01:38:34 AM:

>

>> I use the latest subclipse with eclipse-3.2-m5a and javasvn and

>> subversion-1.3.0.

>>

>> First I made Refactor->Move and then Refactor->Rename. The refactoring

>was

>> successful but I set only one commit (made after refactoring) in the

>> resource history.

>>

>> As far as I know subversion supports renaming. What is the problem?

>

>A move/rename is really just a copy + delete. The history view has an

>option to "Stop on Copy" when showing the history. This is on the

>drop-down view menu. Just uncheck it and the history will keep going past

>the copy.

>

>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

---------------------------------------------------------------------

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org

For additional commands, e-mail: users-help@subclipse.tigris.org

 
Received on Thu Apr 6 05:42:09 2006