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

Re: [Subclipse-users] BUG: file renames don't always have a MOVE_TO or MOVE_FROM IResourceChangeEvent data

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-08-22 02:18:28 CEST

Alberto Ricart <aricart@tibco.com> wrote on 08/21/2006 03:55:51 PM:

> When the files are under subclipse the notifications are similar so
> long as each rename is followed by a commit. If the commit, is not
> provided, and the recently renamed resource is renamed again, the
> notifications are simply a delete and an add. The move information is
> not provided in the resource delta.
> MOVED_TO from: /foo/B.person to: /foo/C.person
> ADDED: /foo/C.person
> [OK - followed by a commit]
> MOVED_TO from: /foo/C.person to: /foo/D.person
> ADDED: /foo/D.person
> [OK, D is scheduled for add, but not commited]
> REMOVED: /foo/D.person
> ADDED: /foo/E.person
> [BAD, the we get a removed notification without either the MOVE_TO or
> MOVED_FROM flags set)
> We would like subclipse to provide MOVE_TO (or MOVE_FROM) information
> in their notification. We have verified that under other team
> providers (perforce being the one we tested) we don't observe this
> behaviour.

This is due to a limitation in Subversion. It does not allow a file to be
moved/renamed twice without a commit in between. We have submitted a
patch to fix this in Subversion and it was just recently committed to
trunk. So it will be available when Subversion 1.5 is released.


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Aug 22 02:19:51 2006

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

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