I have a problem when doing Team -> Update that I have always had with
Subclipse and originally just chalked up to an annoyance, but now it seems
like more of a problem. This problem originally manifested itself when
someone would make a change that updates the .classpath file in a project.
When other people do an update, they get the updated version, but the
Eclipse runtime, in some deep internal area, does not seem to have
recognized the change to the files. I can open the file in a text editor
and see the changes, but if I click on my Project and choose properties,
those dialogs show the old values. I can usually fix the problem by
making some change, and then doing a revert.
We now just experienced the same problem with our plugin.xml files. The
PDE shows the plugins as "Out of Sync" because the version had updated in
the file, but something in the PDE runtime did not seem to know about it.
Also, some new plugin projects that I checked out to my workspace did not
"register" with the PDE at all. It said it could not resolve them when I
referenced them in a <requires> statement. A Rebuild All fixed this
problem, but not the former.
If I had to guess, I would say that Subclipse is supposed to be notifying
the Eclipse framework in some way when it does the Update operation. I
assume that you are wrapping the entire update command in a
WorkspaceModifyOperation as I do not have to do a Refresh for the file
changes to appear. I am not really sure what it is you should be doing,
but something is not happening correctly.
Received on Wed Jun 30 04:03:52 2004