Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 86251 - Package Explorer lacks classes when class filters are used
Summary: Package Explorer lacks classes when class filters are used
Status: RESOLVED DUPLICATE of bug 65240
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-23 07:24 EST by Markus Hanke CLA
Modified: 2005-02-23 09:16 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Hanke CLA 2005-02-23 07:24:10 EST
Steps:
1: create a eclipse project with a source folder "src"
2: create a class T in the default package and a class "p1.p2.A".
3: create a member in class T pointing to class A "private p1.p2.A a;"
4: navigate to Project/Properties/Java Build Path/Source. For the inclusion 
   filter of the source folder "src" enter "p1/p2/" and "T.java"
5: switch the package explorer to hierarchical view.

No class is shown in the package explorer any more.

Variations and observations:
-switch the package explorer to flat view. All packages are shown again.
-for the inclusion filter use "p1/" instead of "p1/p2/". All packages are
 shown again.
-Even if the classes are not shown in package explorer, the class T does
 not show any error.
Comment 1 Dirk Baeumer CLA 2005-02-23 09:16:10 EST

*** This bug has been marked as a duplicate of 65240 ***