Bug 543172 - enum class is Not able to implements interfaces we are getting "No default proposals" is displayimng when we enter im then ctrl+space.
Summary: enum class is Not able to implements interfaces we are getting "No default p...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 4.11   Edit
Hardware: PC Windows 10
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Generic inbox for the JDT-APT component CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-04 08:49 EST by Indresha Mn CLA
Modified: 2023-01-01 04:55 EST (History)
0 users

See Also:

Attachments
enum class is Not able to implements interfaces we are getting "No default proposals" is displayimng when we enter im then ctrl+space. (138.09 KB, image/png)
2019-01-04 08:49 EST, Indresha Mn CLA 		no flags Details
View All 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 Indresha Mn CLA 2019-01-04 08:49:58 EST 
Created attachment 277065 [details]
enum class is Not able to implements interfaces we are getting  "No default proposals" is displayimng when we enter im then ctrl+space.

enum class is Not able to implements interfaces
we are getting  "No default proposals" is displayimng when we enter im then ctrl+space.
Comment 1 Eclipse Genie CLA 2020-12-25 15:27:12 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.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-01-01 04:55:16 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.

--
The automated Eclipse Genie.