Bug 283030 - AJDT installation breaks JDT autocompletion
Summary: AJDT installation breaks JDT autocompletion
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 2.0.1   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL: http://anydoby.com/jblog/index.htm?id...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-09 10:29 EDT by Sergey Zolotaryov CLA
Modified: 2009-07-10 10:34 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 Sergey Zolotaryov CLA 2009-07-09 10:29:46 EDT 
After I have installed AJDT and turned on JDT weaving type-aware autocompletion in Java editor is not working anymore. All the checkboxes are selected in the Java/Editor/Content Assist/Advanced preference page, but they are just ignored, as it seems.

The only solution which I found so far is to DISABLE JDT Weaving service.

You can see the example code which does not work following the issue URL.
Comment 1 Andrew Eisenberg CLA 2009-07-09 11:44:14 EDT 
Thanks for the bug report.  I'll take a look at it.
Comment 2 Andrew Eisenberg CLA 2009-07-09 16:09:45 EDT 
In your eclipse preferences Java > Editor > Content Assist > Advanced page, uncheck 'Java Proposals' and check 'Java Type Proposals' and 'Java Non-Type' proposals.  Does this work for you?
Comment 3 Andrew Eisenberg CLA 2009-07-09 19:44:09 EDT 
OK.  I did find some situations where auto fill for method arguments were still not working.  I am fairly certain that I have addressed all the cases.  The fix will be available in the next dev build in the 3.5 stream, which should be available in the next few hours if the build server is being helpful.

If you see any problems after you upgrade to the dev build, please re-open this bug.
Comment 4 Sergey Zolotaryov CLA 2009-07-10 10:34:08 EDT 
Suppose I am not the person to CLOSE the bug, but I confirm that the issue is now fixed.