Bug 392135 - [open type] Open type does not respect access restriction filters
Summary: [open type] Open type does not respect access restriction filters
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 392362
Blocks:
  Show dependency tree
 
Reported: 2012-10-17 03:15 EDT by Dani Megert CLA
Modified: 2020-05-10 00:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2012-10-17 03:15:06 EDT
3.7.

The 'Open Type' dialog does not respect access rule filters, but this would be expected when looking at the 'Type Filters' preference page:

Type references with access restrictions:
[x] Hide forbidden references
[ ] Hide discouraged references

We should do the same for all type filters on that page, especially because that's what we also open via 'Open Type' dialog.
Comment 1 Markus Keller CLA 2012-10-18 13:28:40 EDT
Bug 296277 was incomplete since it doesn't work for the JavaWorkspaceScope, see bug 392362.

In addition, the Open Type dialog didn't check the access rules. Fixed that with http://git.eclipse.org/c/jdt/eclipse.jdt.ui.git/commit/?id=2936d56ca3ac16b9addfd38534a409d92605e873

Now, access rules work fine unless Open Type works on the full workspace. If you select a working set (and then close/reopen the dialog to refresh), the access rules are correctly applied.
Comment 2 Eclipse Genie CLA 2020-05-10 00:12:57 EDT
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.