On Fri, Jul 11, 2008 at 1:14 PM, Hugo Visser <joegi_at_scene.nl> wrote:
> This week our team has switched to subversion and some of the team members
> have already been bitten by the deletion handling in subclipse. Searching
> the list I saw it just came up again on may 7th, but aparently still no
> fixes. I would like to give it a shot myself, but I need some help to get
> going.
>
> Basically what I was thinking is this:
>
> - Let the file be scheduled for delete as usual
> - When the same file / folder / tree is "added" again, treat it as a
> modification (issue svn add on it). Usually this is what was intended and it
> also fixes the double event bug/feature in Eclipse.
>
> This is probably a bit too simplistic and may not cover all use cases, if so
> please let me know :)
>
> The other thing is that I'm not too experienced in Eclipse plugin
> development and the subclipse code structure. I've checked out the
> ..subclipse.core project along with some others, but the core seems to have
> the things I'm looking for like resource status classes and the
> SVNMoveDeleteHook.
>
> Any hints (some url's or some instructions) to get me started devving and
> debugging would be greatly appreciated.
I'd start by explaining the problem you are trying to solve. What
needs to be fixed about deletions?
Following a delete with an add is not a solution. That does not turn
it back into a modification, it turns it into a replace, which means a
new line of history is created.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-07-11 19:21:28 CEST