Summary: | Option to list weaved components | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Gerard Toonstra <toonstge> |
Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | DEVELOPMENT | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: |
Description
Gerard Toonstra
2004-10-13 20:29:57 EDT
Does the '-showWeaveInfo' option meet your requirements? (which has only been recently added to AspectJ). If passed on the command line, for example in building this demo project tjp: ajc -showWeaveInfo Demo.java GetInfo.java results in: Type 'tjp.Demo' (Demo.java:19) advised by around advice from 'tjp.GetInfo' (GetInfo.java:26) [with runtime test] Type 'tjp.Demo' (Demo.java:29) advised by around advice from 'tjp.GetInfo' (GetInfo.java:26) [with runtime test] Type 'tjp.Demo' (Demo.java:33) advised by around advice from 'tjp.GetInfo' (GetInfo.java:26) [with runtime test] --- This option can be also be supplied in the UI (AJDT) in the project properties AspectJ page. Or in an imminent dev build of aspectj you can supply it in an ANT iajc call. The one piece of information you might be missing is the method name affected - if you really need it, I could add that to the weaving information produced? Hi there, Thanks for that. It would be sufficient at the moment. I don't think my version supports it yet ( 1.2 ), but I'll look at it some time later. At the moment I am struggling to get Eclipse working efficiently again after downloading AJDT. ( 100% CPU consumption, infinite loop of some kind, etc. ), for which I might file another bug report soon as I get more info what might cause it. If the method names could be added *easily* than that would be a very good addition ( as long as method overloads are distinguishable ). I haven't yet been able to run it with the extra info, but does the name of the class include the package as well? Thanks for the quick reply, Gerard Closing out bug as per last comment from Gerard. |