Community
Participate
Working Groups
I am using two projects: A and B. Project B uses some classes from project A, contained in a jar file, which is in the classpath of project B. If I remove a method from one of project A's classes, build a new jar file and copy the new jar file to project B, I still can see the removed method in the content assist list for the changed class. A refresh was automatically done, because I instantly (auto build on) get a compilation error, if I referenced the removed method in project B. Explicit refresh or clean project does not help, the content assist list is only updated when I restart eclipse. The same problem exists, if I add a method to one of the classes and copy a new jar file to project B. And this is, where it gets annoying: I cannot see any new methods from my newly built jar file, so content assist is quite worthless in this case. Bug seen in 3.2.0 and 3.2.1, had worked correctly in 3.1
This problem isn't only a code assist problem. The reconcile suffer from the same bad behavior. Codeassist and reconcile use a SearchableEnviroment which use a NameLookup. The problem seems to come from the NameLookup which return classes of the old version of the jar.
One of my colleagues found a workaround to get the new classes without having to restart eclipse: If you remove the jar from the buildpath and add it again, the problem is gone. Since you can just right-click on the jar in package explorer and do a "build path->remove from build path" followed by a "build path->add to build path", this is far less inconvenient than having to restart eclipse.
Any news on this? Will it be fixed in the upcoming version 3.3?
We missed this bug as a duplicate of an already existing one... So, it's fixed since 3.3 M4 and also will be in 3.2.2... If you urgently need this fix for 3.2 you can get the 3.2.2 preview there: http://www.eclipse.org/jdt/core/r3.2/index.php#UPDATES *** This bug has been marked as a duplicate of bug 162621 ***
Verified for 3.2.2 using build M20070112-1200
