Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341167

Summary:	[CommonNavigator] Optionally exclude non-workbench files from Link with Editor behavior
Product:	[Eclipse Project] Platform	Reporter:	Miles Parker <milesparker>
Component:	IDE	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert, prakash, remy.suen
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Miles Parker

2011-03-28 16:36:20 EDT

The Link with Editor functionality results in an overly expanded explorer. (Please see bug 341166.) A major factor in this is that when users are browsing included dependencies, the entire structure for those dependencies is opened. Most notably this happens with PDE plug-in dependencies. It would be nice to be able to prevent this from happening. This may be a PDE / JDT issue but presumably there would need to be support in workbench for this as well.

Comment 1 Dani Megert

2011-03-29 04:53:14 EDT

A workaround for you could be to enable the 'Libraries from external' filter.

Comment 2 Miles Parker

2011-03-29 14:27:58 EDT

Yes, but I want to be able to see the plugins, I just don't want to navigate to them. It's the distinction between editing and viewing here. When I open a plugin class, I'm typically just trying to figure out what is going on in the code, and I don't care what the overall context is. On the other hand, I may want to at some point open up a plugin and manually explore it, for which I can use the "Show In".  It's a subtle distinction, I'll admit, but it comes up a lot in my day to day workflow.

Comment 3 Lars Vogel

2019-11-08 04:36:53 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant please remove the stalebug whiteboard tag.