Re: Again problems with renaming package

> Yes, but it gets a red cross through it. That wasn't even there. It
> was as if only a copy _of the directory without its contents_ with
> another name was made.

 I addressed this in the followup email. That is essentially what
happened. A new folder was created, and then the files were moved. This
doesn't seem to happen if the package does not have any subfolders.

> Before I started all this, I was at a fresh working copy, with no
> changes at all, at HEAD. So I don't understand what you mean. I am the
> only one using the repository (yet), so there is no way that there could
> have been changes.

The out-of-date message comes from the server. I do not see how it can be
wrong. Did you possibly commit some other change to the repository between
the initial update and this commit? That is all it would take.

> Indeed, but this _is_ an Eclipse bug right? It should refactor all its
> subpackages as well.

I do not know. Perhaps someone else can comment. I have only used the
feature for real a couple of times over several years. The logical thing
to do would be to try it on a test project that is not connected to a Team
Provider. Perhaps something about Subclipse causes it to behave
differently? I agree that it seems odd.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Sat Oct 8 11:14:36 2005