Re: [ajdt-dev] Clarification if you don't mind!

["Andy Clement" <andrew.clement@xxxxxxxxx>]

Doesn't do that for me - I just see the call advised.  Does your
application execute as expected when you run/test it?  AspectJ will
always do the right thing with respect to matching and weaving, there
are just sometimes issues reflecting that back into the UI.  (For
example, the other recent issue with multiple identical join points on
the same line).

In the first versions of AJDT it did not differentiate between
identical looking call join points anywhere within a method body, and
so all advice was shown in the UI as affecting the first occurrence of
that call join point in the method.  The compiler, however, always did
the right weaving and the program worked.

If you think you have a problem, please raise a bug and provide as
much information as you can:
- what level of AJDT are you on? what level of eclipse?
- is it wrong after a clean full build? is it wrong after an incremental build?
- what OS are you on? mac/linux/win?
- does the application do what you expect when you run/test it?

and maybe attach a screenshot so we can see the issue.

Andy.

2008/7/4 Raffi T. Khatchadourian <khatchad@xxxxxxxxxxxxxxxxxx>:
> On Fri  4.Jul'08 at  8:22:37 -0700, Andy Clement wrote:
>>
>> Looks a  bit broken to me (I only see B, and it is a class), I think
>> you want to raise a bug for that.  I also installed the AspectJ example
>> 'TJP Example' and it did not look right for the aspect there either.
>
> Hm, well I have my example set up as A.java and B.aj, but the problem I
> am getting is that the AJDT says that executions of A.x() are being
> advised! How can that be when the pointcut expression says calls(*
> A.x())??
> _______________________________________________
> ajdt-dev mailing list
> ajdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
>