Very rarely, problems present not at build-time but at run-time, with java.lang.VerifyError or incorrect behavior. In these situations, it's most helpful to include the offending class in the bug report. But with load-time weaving, the woven classes are in memory only; to save classes woven at load-time, configure META-INF/aop.xml to dump the classes (by default to an _ajdump subdirectory of the current working directory). Also, if the input class file is not available (e.g., if the AspectJ weaver is after another bytecode weaver), you can also configure the weaver to dump the input classes. For details of how to configure byte-code dumping, see the AspectJ Development Environment Guide section on Configuring Load-time Weaving. Following is a simple example. The following META-INF/aop.xml will weave classes in the com.foo package (and subpackages) but not CGLIB generated classes in the com.foo.bar package (and subpackages). It will also ensure all woven byte-code is dumped both before and after weaving. ]]> You should see messages similar to this: On disk you would find the following files: