Bug 89600 - Content Assist for annotations should only propose annotation types
Summary: Content Assist for annotations should only propose annotation types
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-30 11:59 EST by Markus Keller CLA
Modified: 2009-08-30 02:38 EDT (History)
0 users

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 Markus Keller CLA 2005-03-30 11:59:07 EST 
I20050330-0500

Content Assist for annotations should only propose annotation types:

public class Try {
    @//<- Content Assist proposes class Try
    void m() {}
    @Obje//<- Content Assist proposes class Object
    void n() {}
}
Comment 1 David Audel CLA 2005-04-13 10:00:13 EDT 
CodeAssist does not propose only annotation types because an annotation could be
a member of annother type and the enclosing type of this member must be proposed.
Currently annotation are more relevant in this context.

class X {
  @interface Annot {}
}

We could only propose annotation and type with member annotation but it will be
too costly (top level types should resolved and resolution is currently too costly).

Deferred post 3.1.
Comment 2 Eclipse Webmaster CLA 2009-08-30 02:38:24 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.