Community
Participate
Working Groups
Build ID: I20070625-1500 Steps To Reproduce: When using Generics in the class declaration (e.g., "public class C1<T>"), extending classes (e.g., "public class C2<String>") that call the @AspectJ labeled methods don't have markers (or woven classes). I will attach a jar file with an Eclipse project that will show the problem.
Created attachment 74512 [details] Test Project The files in this jar should show the problem... I marked the lines where I think there should be a marker (advice) with the comment "// Should be a marker here..."
Created attachment 74513 [details] Test Project The files in this jar should show the problem... I marked the lines where I think there should be a marker (advice) with the comment "// Should be a marker here..."
I forgot to say that if you remove all of the <...> from the code, all of the markers/advice is correct. The problem only occurs with the use of Generics.
:( Wish I'd got to this bug sooner. Quite serious. I've now fixed it. thanks for the clear test case. Can't believe more people haven't hit it. The problem was not deferring to the backing generic member to determine annotation matches when working with a parameterized method.
