Community
Participate
Working Groups
I have been having this problem with all versions of eclipse for the past 2 years. I have a workspace with about 20 projects, using a number of user libraries that I have defined. I have one called SWT which points to an swt jar (not necessarily the same one eclipse is using). Note: the fact that I'm using the swt jar as an example is purely a coincidence; this seems to happen with many other user libraries/jars. When I periodically upgrade to a new version of SWT, I go to the preferences, remove the old jar, and add the new one, from the SWT user library I have defined. Now, most of my projects get build errors trying to find SWT classes. Cleaning all projects has no effect. What I have to do is expand and collapse each project in the tree, then it rebuilds them. This is very tedious with a large # of projects. I have experienced this on Mac OSX, and Linux, up to and including version 3.2.1.
User library container is in jdt.core.
An important part of this bug is that clean should really clean EVERYTHING. The fact that expanding and collapsing a project causes it to rebuild something that wasn't rebuilt by clean indicates to me that the clean process is making some assumptions about what needed to be cleaned and what didn't. The whole point of clean of course, is that the user decides that the IDE has made a mistake. If IDEs never made mistakes, there would be no need for "clean".
I think that this cache should be purged when you do a clean. The reason I think this is that the general reason for doing a clean is that you do not trust the IDE's state, or are having problems with it.
I just wanted to ask if anyone has looked into this bug. It can be quite irritating, and happens pretty much every time we change a user library, to every developer on my team. It has been happening for ages in eclipse, and it seems like it must be affecting others as well. A related issue is that sometimes a user lib has to be removed and added from a project to get it to find the jars in the user lib. I'm not sure if this is due to a user library change, or something else. I do know that my team has to do this regularly. I cannot say if either issue is OS-specific, but I can say for sure that it has been experienced on Linux. I'd be interested in a response from the eclipse team about my suggestions about what clean does and does not do - There is another bug in addition to this one that I filed that would be made easier if clean really cleaned everything. Thanks, Ken
I cannot reproduce using 3.3 RC4. Can you let us know if you still have this issue with last 3.3 build? Thanks
We have seen this behavior in IBM products based on Eclipse 3.0 and 3.2 (WebSphere Developer Studio Client for System i). I'm interested in the outcome of this bug, because the next major version of the tooling will likely be based on Eclipse 3.4.
We have never been able to reproduce this particular bug. However it sounds very much like bug 183117. So I'm marking this bug as a dup of bug 183117. This means that the fix is in 3.3.1.1 and in 3.4M2. *** This bug has been marked as a duplicate of bug 183117 ***
Verified for 3.4M4
