Mark Phippard <markp@softlanding.com> wrote on 10/07/2005 03:33:33 PM:
> news <news@sea.gmane.org> wrote on 10/07/2005 03:19:49 PM:
>
> > Reverting didn't work either, with the same (?) error message.
> >
> > The problem got solved by doing Ctrl-z in the file which I edited
> > manually until nothing was there anymore, and doing a commit then.
> > Strange thing is, Eclipse changes the files also during the renaming
> > process (all package declarations get changed!), but Subclipse does
not
> > complain about that.
>
> I just tried and do not get a problem. Leading me to believe it is
still
> a matter of doing an update.
>
> I refactored a package named x.y.z to x.a.z, then edited the class in
the
> new package and committed all of it.
>
> Let me know if the test had to be something like refactor package x to
y.
One thing I just noticed is that the refactoring of a package works
differently if you are doing a package which has sub-packages. For some
reason, Eclipse only does the package you selected, and not the sub
packages. Consequently, we cannot just do an svn move to do the
refactoring. Instead, we do svn add to create the new folder, and do svn
move on all of the files to move them to the new folder. That explains
the other UI differences.
Since the original folder is not deleted, but no longer has any classes,
it just disappears from the view. As opposed to the other case where it
remains in the view as a delete.
That being said, all of the above worked and Subclipse behaved
surprisingly pefectly. I just had to be at the HEAD revision.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Sat Oct 8 05:46:06 2005