Hi,
Using 0.9.30 I'm usually pretty happy with Subclipse, but today noticed
something odd that I could not explan until I thought further about it.
Suppose you work on a class, rename it (e.g. via Refactor->Rename), modify
the newly renamed class by adding new code and then rename it back to its
original name because you realized the new name wasn't the best idea. It
seems that subclipse does not correctly track this renaming and forgets
about this file's state, so that a commit omits it. I accidentally found
this when my commit done in eclipse didn't show up in another working
copy; inspecting the eclipse working copy with TortoiseSVN it says the
file has been "superseded" (I think - sorry if it's not the right term)
and still needs to be commited.
Am I pushing Subversion's renaming mechanism in general (which still seems
to be based on delete/add in 1.1) or is this something that Subclipse (or
svn) should get right?
Thanks for any ideas -
Holger
Received on Wed Apr 20 00:55:37 2005