Here is some more details about what I am trying to do and may be you
can suggest a better alternative.
I have some aspects with very simple pointcut that pick exception
This aspect will only be used in development, and will not be deployed
We have a large team of developers working on a code base having around
3500 class files.
Weaving all these classes, when a single file changes on the developer
machines will add too much delay to the build cycle.
So I was looking for a way to weave only those class files that were
re-compiled by ant-javac.
This will greatly increase the build speed for average case where
developer only changes few files, compiles, test and repeats the cycle.
Andrew Eisenberg wrote:
Yes, this is because the inpath argument will take all
files located at a particular source root, run them through the weaver,
and spit the results out at a different location. It doesn't make
sense to do this to only a subset of files at a location.
Rather than trying to fiddle with the inpath argument, a better
approach would be to tailor your aspects so that they only touch the
subset of files that you are interested in (eg- using the
On Tue, Jun 30, 2009 at 5:06 AM, Tahir
I am integrating aspectj compile-time-weaving in an existing ant-based
I tried limiting <inpath> with ant's fileset combined with a
selector. But its not working. It appears inpath only supports simple
Is there a way to achieve this?
aspectj-users mailing list