Bug 521756 - Static imports of interface methods won’t work even if added to favourites
Summary: Static imports of interface methods won’t work even if added to favourites
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-01 11:23 EDT by Missing name CLA
Modified: 2022-10-26 01:02 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Missing name CLA 2017-09-01 11:23:20 EDT 
When adding an interface (such as java.util.stream.Stream.* or java.util.Comparator.*) to the favourites list static methods from that interface are still not suggested as static imports.

When a single method (such as java.util.Comparator.comparing) is added to the favourites list that method shows up as a suggestion for a static import. However, the generated import omits the Interface name and for java.util.Comparator.comparing looks like this: java.util.comparing; which obviously won’t work.
Comment 1 Eclipse Genie CLA 2020-07-31 20:12:26 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.

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.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2022-10-26 01:02:48 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.

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.

--
The automated Eclipse Genie.