Summary: | source inclusion mechanism breaks type lookups | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Gabrio Verratti <gabrioverratti> | ||||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||||
Status: | VERIFIED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | ||||||||
Version: | 3.0 | ||||||||
Target Milestone: | 3.0 RC2 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Gabrio Verratti
2004-06-04 15:58:12 EDT
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 |