Compile time weaving doesn't mean you have to recompile swing - by 'compile time' I meant the aspects. At the time you compile the aspects just pass the swing jar in as binary input and ajc will weave the aspects into it, producing a new jar file. You don't need the source for swing.
>From your trace it indicates that no weaver is being created for the classloader that loads the swing classes. If this doesn't happen then that loader will never weave anything. The -Xset flags are only useful if the weaver actually gets to see types with that prefix. I don't know the solution to making the more system'y classloaders associate a weaver instance - maybe someone else on the list does. However, it would be far easier to binary weave the jar containing the swing classes before you launch the app at all. cheers, Andy _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
