Hi Eric, Yes, if you open these files in the Java editor I would expect lots of problems (redlines).
There is an AJDT newsgroup but I don't check it very often. I would report your issue against AJDT in bugzilla (bugs.eclipse.org then tools/ajdt) and, if you can, attach a minimal sample project that shows the issue. > It appears that as soon as AJDT sees intertype declarations on a file, that it drops code completion for anything defined in any aspects. I don't believe that is always the case but I haven't run with this setup in a while. Could even be worth trying with an older STS/Eclipse (Eclipse 3.8 version perhaps) to see if it is a regression in recent eclipses because AJDT is using internal eclipse APIs here and there. If they have changed the APIs slightly we may not have caught it. cheers, Andy On 6 December 2013 17:19, Eric B <[email protected]> wrote: > Hi Andy, > > I do not think that it is anything particularly special. I did catch onto > one thing, although I do not know if this is intentional design, or > problematic, but when my Java code is opened in a Java editor, I get > everything redlined (ie: flagged as error, but no Problem generated). > However, if I open the same file in a AspectJ/Java editor, the redlines > disappear, however code completion still completely fails. > > I have tried the same project in IntelliJ (v13) to see if their editor > functions differently, and again the intertype declarations are not being > shown in the code completion, but at least the non-intertype generated > aspect injections (ie: methods from Roo) are still appearing. > > I will try the dev version of 2.2.4, but I suspect the same thing. It > appears that as soon as AJDT sees intertype declarations on a file, that it > drops code completion for anything defined in any aspects. > > Would providing a sample project help, or is this something easily enough > reproducible? Who/where/how would I report this issue to AJDT? I looked > at the AJDT mailing list, but it looks fairly dead. > > Thanks, > > Eric > > > > On Fri, Dec 6, 2013 at 2:30 PM, Andy Clement <[email protected]>wrote: > >> Sorry I didn't reply sooner Eric. You could try a dev build of AJDT (a >> release is only a blessed dev build, nothing more than that, so it >> shouldn't introduce instabilities). However, I'm not sure any changes have >> gone in that will adjust what you are seeing. >> >> Is there anything unusual about the extra thing you are introducing that >> appears to be breaking things? I presume all the code is compiling clean >> (i.e. no errors in the problems view). Certainly what you are describing >> is an AJDT issue - if there were inexplicable things in the problems view >> it is AspectJ that would be at fault but nothing in the problems view and >> errors in the editor indicate it is AJDT. >> >> Andy >> >> >> On 4 December 2013 08:51, Eric B <[email protected]> wrote: >> >>> 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 >>> >> >> >> _______________________________________________ >> aspectj-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/aspectj-users >> >> > > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > >
_______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
