On 13-12-04 11:24 AM, Eric B wrote:
I'm trying to attach a screenshot of my eclipse window to illustrate what I 
mean.  I don't know if the mailing list accepts attachments, however.

As you can see in the screenshot, methods added in via aspects 
(setLastModified, setAutoUpdateLastModified, setAddress, getId, etc) are all 
flagged as
being errors.  However, the Problem view shows no errors.  The most frustrating 
part of this, of course, is that there is no auto-complete in the
editor when coding.

Sorry - my mistake actually.  The editor is not even proposing my autocomplete 
in regular classes either.  I mistakenly thought it was.  Is this a
problem with AJDT in eclipse?  Are there any newer builds that resolve these 
issues?


Apologies for the multiple postings; I'm slowly starting to understand what has happened. I have recently added an default Interface implementation via an aspect which seems to be causing the issues in these classes. By adding these intertype declarations, it appears that all the code completion for the classes in question is aborted, such that even the Roo generated aspects (non-intertype declarations) no longer work.

This is somewhat difficult to deal with; are there any updates to AJDT that 
will allow for the auto-complete to work?  I'm running AJDT 2.2.3.

Thanks,

Eric


_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Reply via email to