Bugzilla – Full Text Bug Listing
| Summary: | classes in "deep" packages not fully recognized when using tight inclusion filters | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Howard <valencez17> | ||||
| Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | tacpub | ||||
| Version: | 3.1.1 | ||||||
| Target Milestone: | 3.2 M5 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Would need to change INameEnvironment#isPackage(...) to return true if one of the subpackages is included. Created attachment 31874 [details]
Proposed patch and regression tests
Released fix and regression test to HEAD. *** Bug 122983 has been marked as a duplicate of this bug. *** Verified for 3.2 M5 using build I20060214-0010. |
classes in "deep" packages not fully recognized when using tight inclusion filters. This is a problem especially if the source code resides in a hierarchy of folders containing sources that should mostly be ignored. Thanks for any help. - Howard To reproduce: 1. Create empty Java project 2. Create class C in a "deep" (i.e., more than 1 level deep) package. package x.y; public class C { } 3. Create class B to reference class C package z; import x.y.C; public class A { C m_c; } 4. Configure inclusion/exclusion filters [for Java Build Path] to have inclusion patterns: x/y/*.java z/*.java 5. Sources compile but: a. Warnings appear next to import statements in class A. Quickfix does not help. b. Cannot refactor m_c in class A.