Bug 576739 - [content assist] No Java proposals in org.eclipse.pde.api.tools.internal.builder.ApiAnalysisBuilder
Summary: [content assist] No Java proposals in org.eclipse.pde.api.tools.internal.buil...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.22   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks: 575919
  Show dependency tree
 
Reported: 2021-10-19 12:49 EDT by Andrey Loskutov CLA
Modified: 2023-10-29 07:48 EDT (History)
2 users (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 Andrey Loskutov CLA 2021-10-19 12:49:22 EDT 
Import org.eclipse.pde.api.tools into workspace
Open ApiAnalysisBuilder.java
Try to invoke content assist anywhere in the class body (not inside methods) - it shows *no* Java proposals at all.

Try to type hash| to complete to the hashCode() - nothing.

I have no idea what's going on here, and why the content assist doesn't like this class. Other classes from same bundle show no problems with content assist.
I'm using latest nightly 4.22 build.
Comment 1 Julian Honnen CLA 2021-10-20 02:03:34 EDT 
might be the same issue as in bug 575062
Comment 2 Andrey Loskutov CLA 2021-10-20 02:09:23 EDT 
(In reply to Julian Honnen from comment #1)
> might be the same issue as in bug 575062

I don't think so, that class doesn't use switches on strings and I'm trying content assist not inside methods, just in the class body.
Comment 3 Stephan Herrmann CLA 2021-11-06 12:27:01 EDT 
Tried it on today's HEAD as well as traveling back to 2021-10-20 but could not reproduce. Well, I didn't try *every* location in the given class ;)
Comment 4 Eclipse Genie CLA 2023-10-28 17:00:09 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.