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

New svn:keywords behavior in 1.6 is breaking Eclipse refactoring

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 29 Jun 2009 10:04:32 -0400

I do not see anything in CHANGES that explains this, but in SVN 1.6 if
you move a file the keywords in the new file are updated. For
example, the Id keyword is modified to have the new file name and the
LastChangedRevision becomes -1. In SVN 1.5 this does not happen. The
keywords are only updated after you commit.

In Eclipse, when you refactor your code and rename files, the SVN
integration is called so that we can run svn move and properly
register the move. However, since SVN is now altering the contents of
the files, the Eclipse refactoring process no longer works properly.

Is this behavior change intentional? Again, I see no reference to
this in CHANGES. If it is, can we at least make it a config option?
Given that commit will set the proper keyword values I do not see why
move needs to do it.

This is a P1 problem for Eclipse users, and probably other tools that
do renames.

Mark Phippard
Received on 2009-06-29 16:04:48 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.