Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319040 - [CommonNavigator] The .* resources filter does not work in Project Explorer
Summary: [CommonNavigator] The .* resources filter does not work in Project Explorer
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Francis Upton IV CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-06 14:42 EDT by Konstantin Komissarchik CLA
Modified: 2010-07-07 13:26 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Komissarchik CLA 2010-07-06 14:42:45 EDT
The filter that makes it possible hide/show project metadata files does not work in Package Explorer. The .* resources are always hidden regardless of whether the filter is engaged. The filter works correctly in JDT's Package Explorer.

I have verified that this is a problem in Helios and Galileo. Older releases may also be affected. 

Marking this as major as the Project Explorer is becoming the predominant navigational view used by default in many EPP packages. Being unable to turn off this filter makes it more difficult to support users when you need to get them to send you their metadata files.
Comment 1 Francis Upton IV CLA 2010-07-07 10:30:32 EDT
This works for me in Helios I20100608-0911 using the normal Eclipse Platform SDK. I suspect this might be caused by some overriding CNF extensions that are present in your build. Can you provide more details about exactly what build you are using and reopen this?
Comment 2 Konstantin Komissarchik CLA 2010-07-07 12:54:52 EDT
Thanks for looking into this. I didn't realize than an extension can override platform behavior like that. I checked in Eclipse IDE for Java EE Developers and I am not seeing this behavior. Will keep trying to narrow it down to a component.

Could you recommend a way to debug this? Is there a trace flag to enable or a break point to set somewhere? The process of elimination has not produced results so far...
Comment 3 Francis Upton IV CLA 2010-07-07 13:26:49 EDT
> Could you recommend a way to debug this? Is there a trace flag to enable or a
> break point to set somewhere? The process of elimination has not produced
> results so far...
There is good tracing in the CNF that may help you with this, though I'm not sure how well it does with filters.  When you run, in the Tracing tab of the launch config look at org.eclipse.ui.navigator and turn on everything. If you don't get good tracing for the filters, please file an enhancement request about this and we will add it.