[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-users] Xlint:adviceHasNotBeenApplied crossref
|
Er, I think that should have been, Xlint:adviceDidNotMatch... I know there's a message that indicates that there's a join point X that you might think matches an advice Y, but it doesn't, so you get a warning at Y (see also X). I never see the X.
Josh
-----Original Message-----
From: aspectj-users-bounces@xxxxxxxxxxx [mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of Bhaskar Maddala
Sent: Thursday, December 20, 2007 4:38 PM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] Xlint:adviceHasNotBeenApplied crossref
>>> I only get the line where the advice is, which is only half the story;
That actually is the entire story, the advice is not being applied,
anywhere. If the weaver knew where to apply the advice, it would and
you would not receive adviceHasNotBeenApplied.
If you wish you can post the pointcut definition and a small piece of
code where you expect the advice to be applied and then may be someone
could help you.
Thanks
Bhaskar
On Dec 20, 2007 6:35 PM, Caplan, Josh <jcaplan@xxxxxxxxxx> wrote:
>
>
>
>
> Can anyone tell me what configuration I need to use to get the iajc ant task
> to produce the extra bit of output ("see also: line") that should accompaniy
> Xlint:adviceHasNotBeenApplied? I only get the line where the advice is,
> which is only half the story; I'm going nuts trying to find the ineligible
> join point in my code with no help from Eclipse or the command line.
>
>
>
> Josh
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
