Community
Participate
Working Groups
When binary- or load-time weaving against a mixture of woven and non-woven class files a simple scoping pointcut e.g. !within() cannot be used to exclude woven classes and avoid a message similar to: test\pointcut\inner\Main.java error class 'test.pointcut.inner.Main' is already woven and has not been built with -Xreweavable It seems the test for a woven class file happens before pointcut evaluation. A similar problem occurs when trying to exlude classes that cannot be resolved.
Created attachment 12976 [details] Testcase Stand alone binary weaving testcase.
Fix now available in latest build from AspectJ download page.
Adrian put that comment on the wrong bug. 69319 was fixed - so I'm reopening this one.
this would be good to tidy up in M3...
this would be a nice enhancement, but after investigation it is a lot of work and so will be pushed back to 1.5.1
We might like to consider Ron's request at the same time http://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg01894.html. Scoping pointcuts can be used to excluded classes that cannot be resolved. The aim is to make the weaver less aggressive (or greedy).
missed 1.5.1