Community
Participate
Working Groups
ZRH build input + JDT/Core v373c - create fresh workspace - create JUnit project with output folder bin (the output folder seems to be important. Problem doesn't show up with default output folder) - load JUnit 3.8.1 (I attach it to the PR) - select TestCase in package explorer and do a search for references observe: - you get an dialog informing you about inexact matches. Strange ? - the result only contains parts of the matches. For example all "extends TestCase" are missing (e.g. SimpleTest, ....) Refactoring is heavily affected by this problem.
Created attachment 6346 [details] The used JUnit version
Refactoring scenario was bogus (left over of classfiles in source folders), however we should not have been indexing them and failed later on. Fixed in v_374.
Philippe, there isn't any bogus refactoring scenario involved here. I started from a fresh workspace and did a search which reported bogus results.
Oops indeed no refactoring involved, but still the test case did contain extra classfiles which caused grief.
Yes, there are some directories in the zip file which contain class files as well. The problem didn't show up when using v373b since I closed and reopen the project before doing the search. May be that makes a difference.
Fix causes a NPE in DeltaProcessor. Reopening.
Fixed NPE by caching the entry kind earlier in the RootInfo.
Old indexes may contain invalid entry for .class files in source packages. Incremented IIndexConstants.SIGNATURE so as to recompute indexes.
*** Bug 44349 has been marked as a duplicate of this bug. ***
Verified