Project Build Path Visibility and Working Set Constraints

The Eclipse IDE utilizes .classpath and .project files to manage resource visibility and build dependencies. While Working Sets allow for the logical grouping of projects to reduce UI clutter in the Project Explorer, they operate independently of the actual build path configuration.

A design uncertainty arises when attempting to restrict the visibility of referenced projects or external libraries specifically for certain Working Sets without modifying the global build path of the project. Since Filtered Resources only hide files from the UI and do not impact the internal Eclipse Compiler (ECJ) process, there is a disconnect between what is visually grouped and what is functionally available for compilation.

• Does Eclipse provide a mechanism to tie build path visibility to a specific Working Set?
• Can resource filters be configured to prevent specific build path entries from appearing in the UI without removing them from the .classpath?