Community
Participate
Working Groups
At least two seperate type lookups break if I use the source inclusion mechanism. I have a project with a lot of files that I cannot build (due to various unrelated reasons). Prior to my upgrade to M9, I set up exclusion patterns associated to my source folder so that these files would be ignored. Once the inclusion mechanism was introduced (M9?), I was able to simplify things quite a lot by specifying the couple of packages that I was interested in. Now that I specify the source folder contents explicitly via inclusion mechanism, the "Open Type" dialog lookup and the content assist associated with the "Move" refactoring operation no longer pickup any of my types. I can still build, run and debug my sources.
Would you have steps to reproduce this problem ?
Reproducing this is really all too simple. 1. add a class to any package anywhere in a java project 2. build & verify said class can be found by way of Open Type dialog (Navigate- > Open Type) 3. open the build properties for the project, add the new class to the inclusion filter of the source folder containing the new class (I usually only add packages via the "Add Multiple..." command, so I'm not sure if actually adding just the new class by itself has the same behaviour) 4. repeat step 2
The key step is : add packages via the "Add Multiple...". If you add individual files this will work.
Created attachment 11698 [details] Proposed patch Changed IndexAllProject and AddFolderToIndex to visit a folder even if it is not included as it can contain included children.
Created attachment 11699 [details] Regression tests Added regression tests InclusionPatternTests#testSearchWithIncludedPackage1() and testSearchWithIncludedPackage2(0
Released patch and tests
Verified in 200406110010
