> In particular we need to warn them against using -XnoWeave.
-XnoWeave was just deprecated in devguide ajc.xml,1.20, for the next
I also added a note in ltw.xml,1.9 saying that if aspects are required for
to compile, then compile-time weaving is the only option. A longer
along the lines you suggest ("Here's how to move from compile- to load-time
is probably warranted. (For those who want to look now,
information is scattered
through the docs and the developerWorks AOP@Work
articles by me, Adrian,
Ron, and Matt -- if not also various blog entries linked from the AspectJ
From: Matthew Webster <matthew_webster@xxxxxxxxxx>
Date: Fri, Mar-3-2006 6:34 AM
Subject: Re: [aspectj-users] Gentle introduction to Load-time
This shows how easy it is to use LTW when you are using
concrete library aspects which of course is the subject of your blog entry.
One thing our users seem to be struggling with however is making the
transition from compile- to load-time weaving in their existing projects. In
particular we need to warn them against using -XnoWeave.
IBM Hursley Park, Winchester, SO21 2JN,
Telephone: +44 196 2816139 (external) 246139 (internal)
Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
Please respond to
introduction to Load-time weaving
posted a gentle introduction to using an aspect library with
weaving from inside Eclipse and IDEA
uses Spring as the sample aspect library, but the techniques apply
use of LTW. Towards the end of the piece are some useful tips
controlling the weaving process with aop.xml.
Figured it might be
useful to one or more of the readers of this list...
aspectj-users mailing list