Community
Participate
Working Groups
Created attachment 203901 [details] The decorations have disappeared... With Eclipse Indigo (build id I20110613-1736) I have the following problem with CVS. In the Synchronize View, while expanding the nodes of the project tree, when I find a modified file with outgoing changes I often see the right-side grey arrow decoration to appear briefly and quickly disappear. Similarly, files with incoming changes are shown with a left-side blue arrow for an instant, then the arrows disappear. This happens almost always, but not with all of the files. Swiching the model (from "All Models" to "Change Sets", for instance) may make the decoration re-appear on some files and/or disappear on others. I'm going to attach a screenshot of the problem. This problem has never happened with any other previous Eclipse release (from 3.6 back to 3.0).
I just discovered that this problem is not bound to CVS. With Subversive on another workspace I have the same problem, so it must be a problem in the Team component...
I just updated to 3.7.1 (build id M20110909-1335) using the update manager, and I have the same problem, unfortunately :-(
Mauro, any chance for reproducible steps? Is any of the repos you're sync'ing with public?
Unfortunately they are not public. However, I can always reproduce, with both a CVS repository and two different SVN repositories (using Subversive). Also, I reproduce the problem with all the different workspaces I work with. A co-worker of mine reproduces it too, but I really don't know how to help you to reproduce yourself, if you don't see this behaviour :-( Some information I can tell: - CVS server version is 1.12.13 - SVN server version I tested with are 1.6.12 and 1.5.4 - the server I'm using are on a LAN and I access them with server names or IPs (like 192.168.x.y or 10.8.x.y address classes) The only thing I can say is that I never had this problem with Eclipse 3.6 and that it constitutes a serious usability problem...
(In reply to comment #4) > Unfortunately they are not public. Are you able to observe it when sync'ing with a CVS repository @ dev.eclipse.org?
Yes, I am! I did the following: - checked out org.eclipse.core.tools, branch R3_7_maintenance from :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse - created an empty package org.eclipse.core.tools.Test class - edited org.eclipse.core.tools.TreeSelectionProviderDecorator - synchronized with repository the org.eclipse.core.tools project In the Synchronize View, if I leave "All Models", it seems ok, but changing to Change Sets or Workspace models and expanding the tree shows the problem.
Created attachment 205791 [details] Screenshot (In reply to comment #6) > In the Synchronize View, if I leave "All Models", it seems ok, but changing to > Change Sets or Workspace models and expanding the tree shows the problem. This is what I see after I followed the steps from the previous comment. Did I miss something?
Created attachment 205794 [details] My screenshot What you see is correct. This is what I see instead... So, there must be something different in my configuration... the hard point is to find what is causing this behaviour... any suggestion?
I would start with downloading an I-build of plain vanilla Eclipse from http://download.eclipse.org/eclipse/downloads/eclipse3x.php... and downgrading to Windows XP (just kidding). Could you please grab a build of Eclipse Classic and give it a try?
Hi Thomas, I reinstalled Eclipse from scratch (starting from the Platform Runtime), one plugin at a time, and at last I discovered it's Google Plugin for Eclipse 3.7's fault! After this discovering, I also found out this: http://code.google.com/p/google-web-toolkit/issues/detail?id=6660 So, it's not an Eclipse bug. If you wish, please "star" that issue for GPE yourself, since it's very very annoying and it may make people think that it's an Eclipse problem! :-(
(In reply to comment #10) > So, it's not an Eclipse bug. Thanks for sorting this out. > If you wish, please "star" that issue for GPE yourself, since it's very very > annoying and it may make people think that it's an Eclipse problem! :-( Good point, I have voted for the bug in GWT.
