I'm seeing a very similar behavior. When I commit a single file change in
some subdirectory, and check that single file in, I'm then presented with a
list of updates to that entire list of directories, leading to the directory
the file was present in.
The first time this happened, I did as Daniel stated --- checked in a single
change out of several, updated to pick up whatever the directory changes
were, and then noticed that my other changed files were no longer flagged as
having been changed. Refreshing the project returned those files to an
"altered" state.
What I'm puzzled about (other than that) is: why would I be presented with
an incoming set of changes to the entire parent directory structure of my
single file check-in? This is with Subclipse 1.1.7, and subversion 1.4.0 on
Windows.
J
Daniel Serodio <daniel.listas@xxx.com.br> wrote on 10/10/2006 05:23:19 PM:
> I've just updated to Subclipse 1.1.7, and I'm experiencing the following
> problem:
>
> I modified some files locally. No changes happened in the repository. I
> Synchronized, and the Sync view showed some outgoing changes. I
> committed a single file, and the Sync view showed that their parent
> folder was out-of-date. So far, so good.
>
> Then, I updated the project's root, to get these "folder status"
> incoming changes. Now, some of the outgoing changes disappeared from the
> Sync view. Neither refreshing the project nor synchronizing again fixed
> this. TortoiseSVN correctly shows the "forgotten" files as locally
changed.
>
> I restarted Eclipse, and did the same thing again (sync, commit,
> update), commiting a different file, and got the exact same result.
>
> The "forgotten" files are in sub-directories (src/java/...), while
> changed files in the project's root are correctly shown as locally
modified.
>
> Is this explanation clear? What can I do to help diagnose this problem?
> Would a series of screenshots help?
I have to ask first, but you are not switched into Incoming only mode are
you. I am sure you are not but it is worth mentioning.
I don't think screenshots are necessary, I understand the end result. What
would be helpful is a step by step "recipe" that you think causes the
problem. Something like:
Start with a Java project.
Change source from two different packages.
Do a synch.
Commit one of the files.
Update the whole project.
etc...
Mark
Received on Wed Oct 18 10:20:49 2006